Version 15 (modified by 12 years ago) (diff) | ,
---|
- Create account @ https://github.com/
- Fork https://github.com/molgenis/molgenis & https://github.com/molgenis/molgenis_apps
- download github command line version
configure
https://help.github.com/articles/set-up-git
- @commandline try retrieving projects by CLONING (Fork a repository online (molgenis/molgenis)) :
- create folders, cd there and try (Clone it to your HDD) . After forking a molgenis
- repos: git clone git@…:<yourname>/molgenis.git
- git clone https://github.com/<username>/molgenis.git
- git clone https://github.com/<username>/molgenis_apps.git
- git remote add molgenis https://github.com/molgenis/molgenis.git
- git remote add molgenis https://github.com/molgenis_apps/molgenis_apps.git
- git remote
- git remote -v
- Pull from the remote
update project = pull project
- Go into the directory molgenis git pull --all
"commit" = push a change :
- Edit a file vi DEVELOPERS
- git add filename
- git status
- git diff
- git commit -a (Commit the code locally, ) or git commit –m ‘Changed a file’
- git status
- git push origin ( If your done update your ‘fork’ git push, Push the local commits to your repository)
- git push origin master (Add an upstream remote)
On the website: Create a PULL request to: molgenis/molgenis/master This will pack ALL current changes in master to be submitted to molgenis WHICH IS BAD! GOOGLE: “Creating good pull request” ! https://help.github.com/articles/using-pull-requests
Work within a branch.
Create a pull request for 1 branch !
- git branch new_feat
- git branch bug_fixes
- git checkout new_feat
Hack AWAY, all commits are to new_feat, when you push the first time:
- git push origin new_feat
Every morning:
- PULL from the molgenis organisation : *git remote add molgenis git://github.com/molgenis/molgenis.git
- GIT STATUS -> if changes:
- git commit (or git stash)
- Get changes git pull molgenis master Solve any conflict git commit –m “Morning molgenis merge” git push