Allow branch names that have a SHA-1 or SHA-256 prefix.
What does this MR do and why?
Allow branch names that have a SHA-1 or SHA-256 prefix.
As the Gitlab::Git::Commit::RAW_FULL_SHA_PATTERN
constant is not anchored, we need to anchor it where it used to avoid prohibiting SHA-prefixed branch names.
Fixes #455069 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
n/a
How to set up and validate locally
- Create a new branch named
5d2f5139e1ce5dace7854e7e6ccfcacdca48ef98-foo-bar
in a cloned repository or through the GUI. - If in a clone, push it to the remote repository.
Edited by Marcel Stör