git-explode
git-explode copied to clipboard
aspiers
Explode linear sequence of git commits into topic branches
The command used for #7 was: ``` % git explode -p zenspider/zeit_ main zenspider/zeitwerk -d ``` and as you can see, it was creating branches with the names `topic#`
It *looks* like it is ignoring my BASE, but I suspect it is looking at all the surrounding blame hunks. According to `-d` it is looking at a LOT of...
Once it did finish analysis, it crashed: ``` Jul 26 18:14:52 DEBUG Exploding 0e1526a1 ARGH git checkout -q -b topic1 main git cherry-pick 0e1526a1dfed84807adc366ce0278a0cafb008ba Jul 26 18:14:52 DEBUG Assigned topic1...
maybe this is not a git-explode issue, but still I've run into it: `sudo pip install git-deps` results in: ``` creating build/temp.macosx-10.11-x86_64-2.7 building '_pygit2' extension creating build/temp.macosx-10.11-x86_64-2.7/src clang -fno-strict-aliasing -fno-common...
I can't run your extension. As I understand it doesn't work with russian letters. I got an error: > $ git-explode master^ master Traceback (most recent call last): File "C:/Users/zyrianovdv/AppData/Local/Programs/Python/Python36-32/Scripts/git-explode",...
Currently INSTALL.md says to do `pip install git-explode` but that won't work until I submit to PyPI.
I inadvertently passed a base commit that was not an ancestory of head and exploded branch could not be cherry-picked cleanly on top of base (because of head..base changes). pygit2...
It is advertised already, and TopicManager is ready for it too. Wire it all together. Fixes #8