This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date.
This is the process if you want to send a change through Gerrit to the dev branch of upstream Guiders:
As a one-time thing, do:
git remote add jeff-optimizely git://github.com/jeff-optimizely/Guiders-JS.git
- Clone the uptream Guiders repo on GitHub, so you have https://github.com/username/Guiders-JS
- Add this to your local repo:
git remote add username email@example.com:username/Guiders-JS.git
- That will let you fetch upstream from GitHub, and (later, after Gerrit review) do pull requests.
Then, for each new change you want in upstream:
- Get the latest from upstream to your local repo.
git fetch jeff-optimizely
- Start a local branch for your change. Use the naming convention
git checkout jeff-optimizely/dev -b pull_request_some_description
- Before actually doing anything, push this branch to Gerrit without review:
git push origin $(git rev-parse --abbrev-ref HEAD)
- Do your commits as normal. If it doesn't generate a Change-Id, do:
cp other_repo/.git/hooks/commit-msg .git/modules/externals/mediawiki.libs.guiders/mediawiki.libs.guiders.submodule/hooks/
- then do:
git commit --amend
- When you have progress you want reviewed on Gerrit:
git push origin HEAD:refs/for/$(git rev-parse --abbrev-ref HEAD)
Once your change passes review, it will automatically get mirrored to our GitHub. Until then, the branch will still be there, but with only the upstream code. When the Gerrit change is approved:
- Checkout the branch
- Send it to your GitHub fork:
git push username $(git rev-parse --abbrev-ref HEAD)
- Use the GitHub.com interface to send pull_request_some_description as a pull request to upstream.