[feature] git extension - add branch name validation

[raix]

Description:

• Add validation to the git create branch, ensuring that project branch conventions are kept.
• Make the whitespace char - configurable (we default space etc. to underscore - meaning we cannot just past in issue title and be done)

Example implementation:

I can create an initial pr. with the implementation for further discussion, if this is something the vscode team would consider.

eg. if the change should enable extensions to lint/validate the branch name or be a configuration etc.

Kind regards Morten

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Preserve open files list when switching branches (#35307)
• Align git command palette interaction with command line (#15534)

[joaomoreno]

Sure, submit ahead.

[TomasHubelbauer]

Is this really something that should be in VS Code? And not say a Git server hook?

[raix]

@joaomoreno I've added the pr.

@TomasHubelbauer ihmo being able to configure the character used for replacing whitespaces etc. in the branch name cannot be fixed in a hook.
The validation of the branch name it self is a better user experience than a git hook

Question is if this is the solution
or
if making an api available for extensions is a better solution eg. it could interact with github/vsts/jira to match ticket number and copy the title etc. in for you.

[TomasHubelbauer]

Hmm having an API for this would be actually quite interesting, because it would enable your scenario so that VS Code could work the best for you but also allow teams to publish extensions of their own which would check the branch name policies or perhaps even do clever things like suggest prepending current ticket code to the branch name automatically if forgotten etc.

[raix]

@TomasHubelbauer yes would be interesting - I'm currently digging into the vs code source. For now I've attached a gif on the pull request for both solutions.