1

I followed the instructions to fixing a pushed commit message here. It worked well for my local repository. Then I force pushed it back to remote, but the old message is still on git hub. Is this a known issue or am I doing something wrong.

Edit:

https://github.com/crowelab/protocol-captures/commits/master

The second commit is the correct commit message. But when you click on it is still tied to the old commit message (everything is in there, everything is testes"

Community
  • 1
  • 1
jwillis0720
  • 4,329
  • 8
  • 41
  • 74

1 Answers1

2

Remember that the old commit still exists, even after force pushing a new commit (it's just not pointed to from master or HEAD). It sounds like you might be looking directly at the old commit. Remember that the new commit doesn't actually amend the old one, but creates a new one in place, with a different hash.

The right way to check is to check the recent commits at https://github.com/user/repo/commits/master

Yuval Adam
  • 161,610
  • 92
  • 305
  • 395
  • This one did reword the old commit, it did not make a new one. Check the link and you can actually use rebase to reword the commit with the same hash. – jwillis0720 May 06 '14 at 08:22
  • @jwillis0720 that is simply not true. Changing anything about a previous commit requires modifying the history and forcefully pushing the new version (thus breaking any other team members workflow). Check my suggestion before retorting. – Yuval Adam May 06 '14 at 08:25
  • check out the link, i'm still missing something – jwillis0720 May 06 '14 at 12:44
  • @jwillis0720, what do you feel is missing? – Yuval Adam May 06 '14 at 20:56