Merge pull request pantheon-systems#69 from dustinleblanc/68-document…

…-env-vars

pantheon-systems#68: Document git repository authentication environment variables

README.md

@@ -46,6 +46,7 @@ Those can be copied in one command using the [Terminus Build Tools Plugin](https
    * Under Environment Variables in your CircleCI settings add a variable for `TERMINUS_SITE` set to the machine name of your Pantheon site. If you don't know the machine name of your site, look at the URL of the Dev or Test environment of the site. For example in the URL for a Dev environment, `https://dev-pantheon-weekly-demo-site.pantheonsite.io/`, the machine name is `pantheon-weekly-demo-site`.
    * [Create a Terminus machine token using the Pantheon Dashboard](https://pantheon.io/docs/machine-tokens/). Add it as another environment variable in CircleCI named `TERMINUS_TOKEN`.
    * Retrigger a build in CircleCI either by pushing a whitespace (or otherwise inocuous) change to your code on GitHub. This time, the build should pass.
+   * Setup git repository authentication environment variables in CircleCI. For Bitbucket, the required variables are `BITBUCKET_USER`(your Bitbucket username [not email]) and `BITBUCKET_PASS` (An _app password_ rather than your standard password used to login). These variables need to be added to the project environment variables in CircleCI). For Github, this should be the `GITHUB_TOKEN` environment variable. 
 4. (Optional) Under "Advanced Settings" in your CircleCI repository settings turn on "Only build pull requests." While not necessary, this setting prevents separate Pantheon Multidev environment from being created for each commit. With this setting on, all created Multidevs will be named by pull request number and subsequent pushes to an open pull request will reuse the same Multidev environment.
 
 ### Examples