-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
37 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,38 @@ | ||
# git-regret | ||
git regret --hard | ||
`git regret --hard` | ||
|
||
|
||
Do you regret your changes to a GIT repository sometimes? That's when `git regret` becomes useful. | ||
|
||
## How to install it ## | ||
|
||
Simply run | ||
|
||
sudo make install | ||
|
||
to install and | ||
|
||
sudo make uninstall | ||
|
||
to remove it. | ||
The requirements are GIT and Python 3. | ||
|
||
## How to use it ## | ||
|
||
You have to be in a GIT repository to use `git-regret`. | ||
|
||
If you want to delete all changes you have made since the last commit, you would usually execute: | ||
|
||
git reset --hard HEAD | ||
|
||
`git regret` improves this: | ||
|
||
git regret --soft | ||
|
||
If you want to delete the last commit, but retain all changes, you would usually run: | ||
|
||
git reset --soft HEAD^ | ||
|
||
Or you can use `git regret`: | ||
|
||
git regret --hard |