forked from freeCodeCamp/freeCodeCamp
-
Notifications
You must be signed in to change notification settings - Fork 2
FreeCodeCamp Deployment Workflow
Quincy Larson edited this page Aug 20, 2016
·
1 revision
- All code is written and pushed to a branch on the developers' own fork of Free Code Camp.
- Developers create pull requests, pulling code from their branch to Free Code Camp's staging branch.
- Someone other than the person who submitted the pull request QA's the pull request and accepts it if everything is perfect. Otherwise they close the pull request with an explanation of why it isn't perfect, and the developer opens another pull request once they've fixed things.
- Staging is deployed to beta.freecodecamp.com by @berkeleytrue, @benmcmahon100 or @quincylarson periodically.
- Master is deployed to freecodecamp.com once the staging itself is fully QA'd.
- Currently freecodecamp.com and beta.freecodecamp.com share a database, so we must be careful about seeding data and manipulating it on beta.
- This is subject to change once we get better test coverage and continuous integration working.
Learn to code and help nonprofits. Join our open source community in 15 seconds at http://freecodecamp.com
Follow our Medium blog
Follow Quincy on Quora
Follow us on Twitter
Like us on Facebook
And be sure to click the "Star" button in the upper right of this page.
New to Free Code Camp?
JS Concepts
JS Language Reference
- arguments
- Array.prototype.filter
- Array.prototype.indexOf
- Array.prototype.map
- Array.prototype.pop
- Array.prototype.push
- Array.prototype.shift
- Array.prototype.slice
- Array.prototype.some
- Array.prototype.toString
- Boolean
- for loop
- for..in loop
- for..of loop
- String.prototype.split
- String.prototype.toLowerCase
- String.prototype.toUpperCase
- undefined
Other Links