News for hackers. Stuff that matters.
Re:Becoming a Better Software Developer: A Handbook on Perso... by organsnyder on Thursday September 20, 2018 @02:29PM (#18034509)
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).
Re:Becoming a Better Software Developer: A Handbook on Perso... by nicoburns on Thursday September 20, 2018 @04:22PM (#18035160)
Gitlab actually enforces this for PRs with [WIP] in the title
Re:Becoming a Better Software Developer: A Handbook on Perso... by dvlsg on Friday September 21, 2018 @02:34PM (#18041695)
There's a browser extension that does something similar for github too. At least for Chrome, anyways. I imagine it works for other browsers though.
Re:Becoming a Better Software Developer: A Handbook on Perso... by sdoering on Thursday September 20, 2018 @05:20PM (#18035564)
Thank you for that tidbit of knowledge. Learned something tonight.
Re:Becoming a Better Software Developer: A Handbook on Perso... by JohnBooty on Thursday September 20, 2018 @05:41PM (#18035691)
Absolutely, 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.