What. Strict branch naming like feature/, bugfix/, chore/, release/ has been the standard for probably 10 years now in all projects I've been in, often enforced by auto-rejecting pushes that don't comply.
I've used that style in 3 different companies over the last 10 years and I assumed the technique was ubiquitous. This just goes to show the standard deviation in engineering culture is high. There are some large bodies of water but also lots and lots of little isolated tide pools.
Yeah, we've had our CI only run pipelines on proper branch prefixes for many years, so if you for whatever reason had a wip/branch you wouldn't clog up our runners.
Comments
What. Strict branch naming like feature/, bugfix/, chore/, release/ has been the standard for probably 10 years now in all projects I've been in, often enforced by auto-rejecting pushes that don't comply.
I've used that style in 3 different companies over the last 10 years and I assumed the technique was ubiquitous. This just goes to show the standard deviation in engineering culture is high. There are some large bodies of water but also lots and lots of little isolated tide pools.
Yeah, we've had our CI only run pipelines on proper branch prefixes for many years, so if you for whatever reason had a wip/branch you wouldn't clog up our runners.
Never used it in any of the projects I’ve been on.