Pushing a "fixup" commit should not toggle the MR to draft

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

When responding to MR reviewer suggestions, I'll frequently using "fixup" git commits (using the --fixup flag to the git commit command) to indicate that a commit is fixing a prior one. This make it obvious why a fix is occurring, and lets me use the --autosquash flag of the git rebase command to clean things up before merge.

However when I push these commits, GitLab marks the MR as "draft". Our team uses "draft" markers to indicate an MR is not suitable for review, which is the opposite of what I want in this case.

Changing the "draft" status of an MR based on the commit-message is surprising to me as a user. If GitLab does so, it shouldn't hijack commit-message-prefixes which are already used by the git tool for other purposes.

For future searches, the MR activity message was: <User> marked this merge request as draft from <commit sha> <time> minutes ago

Edited by 🤖 GitLab Bot 🤖