Extension:GuidedTour/Upstream change

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:


 * 1) Clone the uptream Guiders repo on GitHub, so you have https://github.com/username/Guiders-JS
 * 2) Add this to your local repo:
 * That will let you fetch upstream from GitHub, and (later, after Gerrit review) do pull requests.
 * That will let you fetch upstream from GitHub, and (later, after Gerrit review) do pull requests.
 * 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:


 * 1) Get the latest from upstream to your local repo.
 * 2) Start a local branch for your change.  Use the naming convention.
 * 3) Before actually doing anything, push this branch to Gerrit without review:
 * 4) Do your commits as normal.  If it doesn't generate a Change-Id, do:
 * then do:
 * 1) When you have progress you want reviewed on Gerrit:
 * 1) Do your commits as normal.  If it doesn't generate a Change-Id, do:
 * then do:
 * 1) When you have progress you want reviewed on Gerrit:
 * 1) When you have progress you want reviewed on Gerrit:
 * 1) When you have progress you want reviewed on Gerrit:

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:


 * 1) Checkout the branch
 * 2) Send it to your GitHub fork:
 * 3) Use the GitHub.com interface to send pull_request_some_description as a pull request to upstream.
 * 1) Use the GitHub.com interface to send pull_request_some_description as a pull request to upstream.