wiki:github_molgenis

Version 17 (modified by antonak, 12 years ago) (diff)

--

configure

https://help.github.com/articles/set-up-git

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

WORD of WARNING

  • NEVER force push origin master
  • If you cannot push, you need to pull ☺
  • Force push destroys your fork !!!!
  • So just never
  • If you did ☹ you should: Directly delete your repository on the website fork, clone,
  • remote add -> molgenis/molgenis again
  • If you have stuff you want to keep:
  • SAVE the files outside of the repos, and commit them back in after you setup a new remote fork and local repository

Git @ eclipse

http://www.vogella.com/articles/EGit/article.html