We manage our development through issues tracking in Scipion GitHub project. + A nicer view of the Scipion issues is provided by Waffle.io
Table of Contents
- How to GIT
- Basic GIT documentation
- List all branches
- Create a new branch and move to it:
- Deleting a branch
- Remote branch
- Submit a bugfix (with branch creation)
- Compare differences
- List the files that are changed between the local and the official repository
- List the files that are changed between two branches
- Apply the differences from one branch into another
- Gitting in Scipion
git config --global user.name "Your Name" git config --global user.email "email@example.com"
git checkout -b NEW_BRANCH
Then you can publish it to origin:
git push -u origin NEW_BRANCH
Locally delete a branch
git branch -d OLD_BRANCH This must be done in a different branch than OLD_BRANCH
The previous command does not allow to locally remove unless the OLD_BRANCH has been merged to another branch. If you want, anyway to locally remove the branch do
git branch -D oldBranch
To delete the branch remotely (after delete it locally):
git push origin :OLD_BRANCH
Everybody else has to “update” the list of branches in the origin, so that they also get it deleted:
git remote prune origin
To create a local branch at the status of a remote branch:
git pull git checkout -b newlocalbranchname origin/remotebranchname
To create a branch and also set to track the remote branch:
git pull git checkout -t origin/branch-name [-b newlocalbranch]
git checkout -b newBranchWithBugFix git commit -m "Your comment" yourFiles git push -u origin newBranchWithBugFix
To see differences between branch A and B:
git diff --name-status A..B
To see differences in a particular file between branch A and B:
git diff A B myFile
git diff origin/branch --name-only
git diff branch1 branch2 --name-only
Let’s say that there is a file in branch2 with some differences with respect to branch 1. Then you want to take these differences and put them in branch 1. From branch 1, you must do
git diff branch1..branch2 yourFile > patchFile git apply patchFile
If you run the git diff without file, then all changes between the two branches are dumped into the patchFile.
Often, when you’ve been working on a part of your project, things end in a messy state. You want to switch branches for a while in order to work on something else. The problem is, you don’t want to do a commit of half-done work (just to be able to get back to this point later). The answer to this issue is the git stash command:
$ git stash
Now you can easily switch branches and do work elsewhere: your changes are stored on your stack. To see which stashes you’ve stored, you can use:
git stash list:
You can reapply the one you just stashed by using the command shown in the help output of the original stash command:
git stash pop
Let’s say you are in the middle of a merging, and you regret from the changes you have already been introducing. Files that are not related to the merging conflicts are unaffected by this command.
git merge --abort
In case of looking for a commit by date, the repository can be moved by:
git co `git rev-list -n 1 --before="2011-06-21 13:37" master`
If you have committed and pushed some changes, you may undo them by
git revert [commitHash]
Since January-2016, we started to follow the git-flow development methodology using git.
Summarizing, there are two main branches: master and devel. New branches should be opened from devel for each new feature that will be included in the next release. Feature-branches should be merged back through Pull Requests in GitHub to allow peer-review and discussions. Master branch should always contain a released status. When we are ready for a new release, we should create a release-branch from devel and only commit bug-fixes to it. When this release-branch is merged (also through Pull Request) to master, it means a new release that should be tagged in master.
The following image illustrates very well this workflow and a very nice explanation can be found [here].
Look for the fork icon (top-right) and make a Fork on your account o institutional account. image::https://help.github.com/assets/images/help/repository/fork_button.jpg[ForkIcon]
git clone firstname.lastname@example.org:YourUserNameHere/scipion.git --origin privatescipion
This should bring your repo to your machine with the remote name “privatescipion”. Feel free to use a different name. It’s yours!
You can keep them, but to avoid confusions, you might want to start with a branchless repo. Well, I guess you need to keep one: Keep master.
git remote add I2PC https://github.com/I2PC/scipion.git
This adds a second remote name I2PC. Again, feel free to name it your way.
In order to catch the branches list from the new repo,
git pull --all
Once you have 2 remotes you have to be more specific when checking out branches from a remote.
To checkout devel, from I2PC type:
git checkout -b devel I2PC/devel
TIP: To check the upstreams (where your local branch will push to) of your branches type:
git branch -vv
Now, when you need a branch to work on something new, that branch should go to your “privatescipion” but start from, usually, I2PC/devel.
git checkout -b mynewfeature devel
now you can work locally as usual with your commits, etc.
Whenever you want to send changes, you must send them to your remote: +git push –set-upstream privatescipion mynewfeature+
Let’s update your “mynewfeature” branch with possible devel changes.
git checkout devel git pull git checkout - git merge devel
Resolve conflicts if any. And push the branch again to your privatescipion with: +git push+
Finally, just create a PR across forks using as base I2PC/devel
= Other useful resources