#random (2022-11)

Discussion on HN: https://news.ycombinator.com/item?id=33536978

Cool, very similar to https://github.com/release-drafter/release-drafter except using branch names instead of PR labels

Ya, pr labels are too expensive. Discipline maintenance is to be minimized as much as possible.

I will never participate in a discussion around versioning based on anything but this. I can’t deal with it after the luxury of this kit. :)

Ilike this:

but I do like labels too, because they are reversible. Especially in open source.

Can never expect contributors to follow various conventions. Easier to label.

I don’t know about labels. Branches are ground level git, something I can make work with any git provider. I’ve had that kit work on all the big 3 at one point or another. Last I checked the core script behind that thing was still working across them.

But yea, I can see where open source projects that take PRs would see this as a potential friction point.

I don’t know much about renaming branches. I would assume you’d loose any interactions against an open PR. Still not much work to add branch naming scheme to the contribution docs, or add a pr check against it.