tags:

views:

253

answers:

2

Since asking my last question which turned out to be about rebasing with GIT, I have decided that I don't want to rebase at all. Instead I want to:

  1. Branch
  2. Work work work, checking in and pushing at all times
  3. Throw out all of those commits and pretend they never happened (so one clean commit at the end of work)

I do this currently by copying the files to a new directory and then copying them back in to a new branch (branched at the same point as my working branch), and then merging that into master or wherever.

Is this just plain bad and why? More important: Is there a better/GIT way to do this? git rebase -i forces me to merge (and pick, and squash).

+4  A: 

The easiest thing to do is a soft reset.

So checkout your topic branch:

git checkout -b topic master

work, work, work.

git commit
git commit
git commit
git commit

Happy with this, you can make a new single commit on top of master

git reset --soft master
git commit

Now merge to master (it will be a fast-forward) and tidy up the topic branch. (Note that you don't need to do this if you are prepared to remember or tag where master was and just work on master without branching, you could have just done git reset --soft old-master and git commit and you wouldn't need these last clean-up steps.)

git checkout master
git merge topic
git branch -d topic
Charles Bailey
Excellent (+1), but that leaves the question: is this the right way (with Git or actually with any (D)VCS)? all the logical incremental steps are squashed, and if there is some nasty bug withing the commits for topic, that won't be easy to pinpoint and fix.
VonC
@Charles Bailey, thanks for that. @VonC, it depends. I check in every minute or less... too much information is just as bad as none.
Yar
So just to be clear, git reset --soft some_branch switches me to some_branch/some_commit without touching my files?
Yar
Okay, I see it now: it resets me there, but doesn't do a checkout. Strange/great!
Yar
`git reset --soft` just moves the current branch head to the given commit, leaving the index in tact. A normal (`--mixed`) `git reset` also resets the index to the state of the given commit but that isn't what you want for this scenario
Charles Bailey
A: 

You can also use git merge with the --squash option.

Ionuț G. Stan
Squash happens on every commit automatically, I don't see how that helps with my question. Not that it doesn't, but I'd need more information.
Yar
I've used `git merge --squash` when I wanted to merge a topic branch with master, but also reduce the commit history to just one commit. `git merge --squash` performs the merge, but let's you supply a commit message before actually committing the merge. So the end result appears as though you have committed just once to the master branch.
Ionuț G. Stan