Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: cover Git 2.32.0, check for amend! commits #26

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ErichDonGubler
Copy link

@ErichDonGubler ErichDonGubler commented Sep 10, 2021

This adds coverage for the new amend! commit prefixes added with the --fixup={reword,amend}... variants.


I'm unclear on whether or not this would be considered a breaking change?

Closes #25.

This adds coverage for the new `amend!` commit prefixes [added with the
`--fixup={reword,amend}...` variants][git-2-32-announcement].

[git-2-32-announcement]: https://github.com/git/git/blob/8b7c11b8668b4e774f81a9f0b4c30144b818f1d1/Documentation/RelNotes/2.32.0.txt#L44-L48
@13rac1 13rac1 self-requested a review December 21, 2021 19:17
@MartinDelille
Copy link

A nicer solution would be to make configurable the list of forbidden string in the git history (I would personnaly enjoy to add "wip!" for example)

@ErichDonGubler
Copy link
Author

A nicer solution would be to make configurable the list of forbidden string in the git history (I would personnaly enjoy to add "wip!" for example)

AFAIK these aren't part of the normal autosquash flow in Git, which is what this PR was motivated by. Not saying whether or not your suggestion should be implemented, just noting the context here.

As for your request, I suspect another issue would be the most effective way to drive discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Doesn't handle !amend commits
2 participants