Size: 1754
Comment:
|
Size: 2299
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 66: | Line 66: |
= GitHub Workflow = You found a project you want to contribute to. 1. Fork the project (on git hub - now you should have a copy in your repository that is separate from the original) 1. Create a branch of the project (i.e. git checkout -b [branchname]) 1. Edit files as needed 1. Commit -a -m "Message" (i.e. add/commit changes) 1. push to your forked git repository on github: git push origin [branchname] 1. Check github for a link to a pull request. See the video [[https://www.youtube.com/watch?v=rgbCcBNZcdQ|here]] |
Starting a git repository?
First setup the remote repository:
ssh git@brain2.scotnpatti.com cd /home/git/repos # you shouldn't use the base user directory for good reasons -- See SshGen page mkdir my_project.git cd my_project.git git init --bare git update-server-info # If planning to serve via HTTP exit
On your local machine:
cd [your project directory] git init git add * # or "." if you want to add all the files in the hierarchy git commit -m "My initial commit message" git remote add origin git@example.com:repos/my_project.git git push -u origin master
Others can now clone track the remote repository:
git clone git@example.com:repos/my_project.git cd my_project
Adapted from: http://thelucid.com/2008/12/02/git-setting-up-a-remote-repository-and-doing-an-initial-push/
Standard workflow
edit/stage/commit
git status # View the state of the repo git add <some-file> # stage a file git commit # commits changes
Publish
git push origin master
You may get an error...
Updates were rejected because the tip of your current branch is behind its remote counterpart. Merge the remote changes (e.g. 'git pull') before pushing again.
So you may need to pull by doing the following:
git fetch origin master git merge origin master git pull origin master
If you have changes, go edit the file to remove the conflicts (Visual Studio Code works great for this, better than Visual Studio 2017).
You may then get a CONFLICT (content): Merge conflict in <some-file> which you will need to resolve by type git status Actually you should do that before you do anything.
GitHub Workflow
You found a project you want to contribute to.
- Fork the project (on git hub - now you should have a copy in your repository that is separate from the original)
- Create a branch of the project (i.e. git checkout -b [branchname])
- Edit files as needed
- Commit -a -m "Message" (i.e. add/commit changes)
- push to your forked git repository on github: git push origin [branchname]
- Check github for a link to a pull request.
See the video here