Update configuration to use master vs. bramble

.travis.yml

@@ -7,7 +7,7 @@ before_script:
 script: grunt build-browser-compressed
 branches:
   only:
-  - bramble
+  - master
   - production
 notifications:
   irc: "irc.mozilla.org#thimble"
@@ -28,7 +28,7 @@ deploy:
     detect_encoding: true
     on:
       repo: mozilla/brackets
-      branch: bramble
+      branch: master
   - provider: s3
     access_key_id: AKIAI7XHSZFYVHFRTRIA
     secret_access_key:

README.md

@@ -20,8 +20,7 @@ for info on how we're using CodeMirror.
 
 # How to setup Bramble (Brackets) in your local machine
 
-Step 1: Make sure you fork and clone [Bramble](https://github.com/humphd/brackets).
-We do our work on the `bramble` branch, so make sure you aren't on `master`.
+Step 1: Make sure you fork and clone [Bramble](https://github.com/mozilla/brackets).
 
 ```
 $ git clone https://github.com/[yourusername]/brackets --recursive

env.dist

@@ -3,7 +3,7 @@
 #
 
 ## Which branch is considered master?
-export BRAMBLE_MAIN_BRANCH="bramble"
+export BRAMBLE_MAIN_BRANCH="master"
 
 ## Which remote is considered upstream?
 export BRAMBLE_MAIN_REMOTE="upstream"

invalidate.js

@@ -17,7 +17,7 @@ var cloudfront = new AWS.CloudFront();
 // invalidate staging or prod
 var invalidationPath;
 var distribution;
-if (process.env.TRAVIS_BRANCH === 'bramble') {
+if (process.env.TRAVIS_BRANCH === 'master') {
   invalidationPath = '/bramble/staging/dist/*'
   distribution = 'staging';
 } else {