3 ms·
My previous team had a convention of putting a prefix "[DO NOT MERGE]" on the subject line of RFC-style PRs. Worked well enough, though it would have been nice
by organsnyder 8y ago
My previous team had a convention of putting a prefix "[DO NOT MERGE]" on the subject line of RFC-style PRs. Worked well enough, though it would have been nice to have the tool enforce that also (even a checkbox like "prohibit merging" would have worked).
- nicoburns 8y agoGitlab actually enforces this for PRs with [WIP] in the title
- JohnBooty 8y agoAbsolutely, this. We did the same thing -- [DONT MERGE] or [WIP] in the title. That way you could get feedback from other devs, and pushing commits to your PR would trigger CI runs so you could be made aware of any build failures you were causing. (The builds took hours, sometimes, so running the full test suite locally was impractical) We used Github but I'm sure it would work in a lot of workflows.