git-gud
git-gud copied to clipboard
benthayer
Wanna git gud? Then get git-gud, and git gud at git!
A level to show that the commit isn't necessarily the same as the working directory. Start with no commits. The working directory will have a file in it, and the...
People can get confused about the staging area: - They create a file and think "git commit" will already know about it and will commit it - They create a...
Using `git rebase` multiple times, make the commit messages say "This level has to be done in reverse order" Branches would be as follows, with each word being its own...
Spawned from #197 . https://github.com/benthayer/git-gud/issues/197#issuecomment-671157907: > Hmm...just to make sure, would you like some sort of error handling so that the error is hidden from the user unless they run...
Right now, the level template copies over several files which aren't necessarily used. For example, test.spec might not be used if a level is fairly simple, and filename.txt is copied...
When commands fail, they should fail with status code 1, which could help us make sure users are never seeing an error that's coming from python.
Words tend to be cut off and finished on a new line when we just print them out directly, so word wrap would be a great usability feature.
Git has the feature where we can set aliases for commands. It would be nice if git gud did the same thing. For example: `git gud config alias.c "commit"`
A custom level looks something like this. It's not much different than a normal level, but they are used frequently for custom status messages and other things. Having these automatically...
This issue has been split up into several levels The skill name is `rewriting` - [ ] Amending #255 - [ ] Interactive Rebase #256 - [ ] The Same...