Once you've completed your updates, you can make them publicly available by pushing them up to your forked repository at GitHub.
New BranchesIf this is a completely new branch that's never been pushed up, you will need to run a git push command that will create the branch on the forked repository:
git push <your_GitHub_account> <localdev>:refs/heads/<localdev> The arguments passed to this command are
- The remote nickname for your forked repository - <your_GitHub_account>
- The name of the local branch - <localdev>
- The name of the branch to create on the forked repository - refs/heads/<localdev>
The ":" is used to create a mapping in the command between local branch <localdev> and remote branch name "refs/heads/<localdev>". You need to fully specify the remote branch (with "refs/heads") or Git will throw an error because the branch cannot be found.
After the push is complete, you should configure the local branch to track the remote branch:
git config branch.<localdev>.remote <your_GitHub_account>
git config branch.<localdev>.merge refs/heads/<localdev>
The explicit push command and the branch configuration only needs to done once.
Existing BranchesIf you're pushing updates from a branch that already is tracking a remote branch, all you need to do is execute
git push
Git will use the branch configuration to determine the correct remote connection (<your_GitHub_account>) and will automatically push all the branches in your local repository that match with branches on that remote connection. (This will include the master branch!)
Sending a Pull RequestOnce you've pushed your changes up to your forked repository, you can send a pull request via GitHub to notify us (or anyone else in the Insoshi network) of your update.
You should include as much information about the changes you've made:
- Lighthouse ticket (if there is one)
- Commit ID (in case you're making additional pushes afterwards)
- A quick description of what's been updated/added/changed
| 