Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

move changes from production to staging and then push them to git; and vice versa #8

Open
swinter2011 opened this issue Mar 8, 2016 · 2 comments
Open

move changes from production to staging and then push them to git; and vice versa #8

swinter2011 opened this issue Mar 8, 2016 · 2 comments

Comments

@swinter2011
Copy link
Collaborator

No description provided.

@swinter2011 swinter2011 changed the title move changes from production to staging and then push them to git move changes from production to staging and then push them to git; and vice versa Mar 8, 2016
@swinter2011
Copy link
Collaborator Author

cherry pick changes from one and go to the other

@swinter2011
Copy link
Collaborator Author

staging is the default branch - we're going to cherry pick from production and put them in staging. we're going to blow away production and then create new branch off of staging; on heroku and github you'll have to force overwrite the new production branches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swinter2011