Re:Google App Engine now supports Git Push-To-Deploy
by zimbatm on Thursday June 13, 2013 @08:55AM
(#5873748)
Here is how I work on heroku, use a branch, rebase and force push to clean your commit logs:
git checkout -b heroku-setup
# make some commits
git push -u heroku heroku-setup:master
# oops, something was wrong
# make some more commits
git push
# ok, everything is working
git rebase -i origin/master
# squash/remove commits
git push -f
# test one last time
git checkout master
git merge --no-ff heroku-setup
git push
Re:Google App Engine now supports Git Push-To-Deploy
by tokenizerrr on Thursday June 13, 2013 @08:55AM
(#5873749)
You can rewrite history. This is a bad idea if other people are collaborating on your project, as the new history will be mismatched with theirs. It can still be done safely when properly collaborated, or if you're alone just go for it.
http://gitready.com/intermediate/2009/01/31/intro-to-rebase....
Re:Google App Engine now supports Git Push-To-Deploy
by schrodinger on Thursday June 13, 2013 @08:36AM
(#5873666)
Just use git push -f. Or just push from a branch.
Re:Google App Engine now supports Git Push-To-Deploy
by X-Istence on Thursday June 13, 2013 @01:45PM
(#5875413)
So long as the target you are deploying too can't also get pulled from in the mean time you can amend commits all you want and push as often or as little as you want.
There is no need for junk commits.
I deployed my first project to Heroku a few weeks ago, and now my project history has a handful of permanently unremovable junk commits, which I made solely to force Heroku to rebuild my app.