Can tags be automatically moved after a git filter-branch and rebase?

I’ve written a script that does this. $ git-rebase-tags master Rebasing 107 tags onto ‘master’ Can’t rebase tag ‘staging-deploy-01’ because there are no identical commits on ‘master’ Pointed tag ‘v0.0.11’ at commit 81e16f2ca1bc7802547bf19c1dba1a68212eafff Pointed tag ‘v0.0.12’ at commit 17051cc28084dd56ae56e96767bceee46217c02d Pointed tag ‘v0.0.13’ at commit 5d795076ba4b33f81d327dcf9bff727cef7771a2 […] See gist.github.com/908381. But even better, use the –tag-name-filter option … Read more

Git rebase –preserve-merges fails

TL; DR The –preserve-merges flag simply tells git-rebase to try to recreate merge commits instead of ignoring them. It does not give git rebase the ability to remember how merge conflicts were resolved, i.e. it does not record conflict resolutions for future use. What you want to use for that is rerere. In your toy … Read more

git rebase merge conflict

Rebasing can be a real headache. You have to resolve the merge conflicts and continue rebasing. For example you can use the merge tool (which differs depending on your settings) git mergetool Then add your changes and go on git rebase –continue Good luck

Remove commit for good

I contacted Github staff from here : https://github.com/contact Here’s the answer (I couldn’t do anything about it, no prune, no gc, etc) Hey Maxime, The commit was available because commits are not automatically deleted when they’re removed from the history of a branch — they’re deleted when they’re garbage collected. I just ran garbage collection … Read more