Allow for fixup! commits

[blaggacao]

When using conventional commits, allow the use of fixup! <sha> or fixup! <header> syntax, which are both recognized by git rebase --autosquash later on.

[sdurrheimer]

Agreed, fixup! and squash! prefixes should be ignored as those mechanisms are part of the base features Git offers.

[janderssonse]

@blaggacao I did'n try this, but I think this could be solved by a setting in the .conform.yaml, just adding allowed types:

conventional:
      types: ["fixup!,"wip", "chore","docs","perf","refactor","style","test","release"]

[blaggacao]

That's a good idea, however we eneded up wrapping with a regex condition.

That gives more flexibility to the actual header and thereby less restriction to the end use: divnix/std@2f047e0

[janderssonse]

Any way that works is the right way! :) Sidenote, I really like this tool, but would love to see more documentation, and more responses to the issues from the maintainer.

[terlar]

The type fixup! and squash! won't work since it is in the format of fixup! previous commit message so it doesn't follow the format, it would have to be fixup!:. It would be nice with support for this without having to wrap conform in a shell script.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.

[qqii]

Any chance for this to be reopened? I'd love to see the following supported:

fixup! <commit_ish>
squash! <commit_ish>
amend! <commit_ish>

Adding them to the types is not enough as the regex enforces a colon:

var HeaderRegex = regexp.MustCompile(`^(\w*)(\(([^)]+)\))?(!)?:\s{1}(.*)($|\n{2})`)

Edit: I've made an attempt at implementing this in #282.