Last active
November 28, 2016 20:36
-
-
Save BooneTeam/4925eeae8d0826d90df3d4de0f02f63d to your computer and use it in GitHub Desktop.
typical workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Production/Staging workflow Steps | |
Make Heroku App for Staging | |
Make Heroku App for Production | |
Add remote for production | |
heroku git:remote -a <APPNAME> -r <REMOTENAME> | |
add remote for staging | |
heroku git:remote -a <APPNAME> -r <REMOTENAME> | |
always merge and push to staging before master | |
git push <REMOTENAME> <FROMBRANCH>:<TOBRANCH> | |
for staging app | |
ie: git push staging staging:master | |
for prod app | |
ie: git push production master:master | |
so a typical feature would be | |
1. pull master | |
2. branch on a feature | |
3 .push to feature branch | |
4. merge to staging branch | |
5. push to staging app | |
6. test app on staging live | |
7. if all ok merge staging branch into master branch | |
8. if no merge conflicts etc push and deploy to production app. | |
9. if any changes take place deploy master to staging app to make sure no breaking changes, then deploy to production |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment