Is it possible to control the branch name of the PR about action

[Andarist]

This sounds really arbitrary to me. I understand (to some extent 😉 ) that you might require a certain pattern for your other branches as maybe they need to reference some tracker issue numbers or whatever, but it should be totally possible to customize this on your end. I mean - it should be possible to extend your validation rules with special cases for our branch names.

it would be great to have control over as we have with title and commit msg

Customizing those seems like a much more popular option than customizing the branch name. I'm not 100% opposed to making this configurable, but your feature request really comes as a quirky one to me. I'd like to discuss alternatives first.

[tragiclifestories]

@Andarist one good reason to disallow path separators in branch names is because when it comes down to it, refs are stored in .git as files and directories. So there is a scenario like this:

1. Dev A pushes branch foo to remote.
2. Dev B pushes branch foo/bar to remote.
3. CI cannot run tests on foo/bar because the git metadata is unavailable.

For this reason, we have a global rule across our whole organisation that disallows path-separators in branch names. It has bitten us in practice multiple times and requires manual git-surgery to fix. So it would be great if this issue could be reconsidered.

[0mnius]

We don't use folders in branch names (what / does) and use only lower kebab...it would be great to have control over as we have with title and commit msg

[Andarist]

Why can't you just tweak your branch name validations 😉 ? What kind of a name would comply with your rules?