Branch name validation script

[erenbesel]

Problem

We realized we currently only have branch rules for develop, meaning any PR targeted to any other branch than develop can be freely merged without our branch rules (e.g., 3 approvals, resolved conversations, green CI etc).

Solution

Github allows creating rules for specific branches but that would mean we would need a new rule for every new branch which is not sustainable. Fortunately Github also allows rules for branch folders such as feature/* so we can create branch rules under such folders.

This would require all future branches to be created with these prefixes. This PR achieves it with a script and add it in our pre-commit hook.

Currently naming format is {labelName}/{branchName}

labelName = feature, fix, chore, improvement, release

branchName = Any name ( can be made to always include COIOS string)

Ticket

COIOS-870

[atmamont]

Should we enable base PR checks for new branches subset?

[github-actions]

✅ No changes detected

Comparing improvement/branch_name_validation to develop

---

Analyzed targets: Adyen, AdyenActions, AdyenCard, AdyenCashAppPay, AdyenComponents, AdyenDelegatedAuthentication, AdyenDropIn, AdyenEncryption, AdyenSession, AdyenSwiftUI, AdyenTwint, AdyenWeChatPay

[goergisn]

Looks great!

Some potential improvement for the future would be validating the version number if it's a release branch

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud