Feature branches
Paul Dale PublicSeen by 19What do folks think about a "feature branch" tag that gets added automatically to PRs destined to merge to a feature branch?
Isn't it enough it the PR has the feature branch as base?
Given that I've merged a feature branch PR to master and come close to doing so a couple more times, I'd prefer something a bit more in my face and brightly coloured.
I've already added a label `branch: feature`. If anybody adds a CI workflow automatically assigning it to PRs that have a `feature/...` branch as a base branch, I certainly won't be against it.
I think its a fine idea. It might also be good for ghmerge to warn if the target specified by the --target option (or the default) doesn't match the target specified by the PR and warn in that event.
Good suggestion