{"version":"2.1.290","anchor":"git-branch-name-validation-loosened","canonical_anchor":"git-branch-name-validation-loosened","heading":"Git branch-name check runs fewer tests","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/git-branch-name-validation-loosened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Git branch-name check runs fewer tests\n\nA git branch-name check no longer limits name length, rejects HEAD or a leading dash, or limits each part's size\n\n**Unclear.** The removed tests may have moved elsewhere, and this may be a different check rather than the old one changed.\n\n**What**\n\nA check that decides whether a git branch name is valid now runs fewer tests. It no longer checks:\n\n- the overall length of the name\n\n- `@`, `HEAD` or a leading `-`\n\n- the size of each part of the name\n\nIt still checks the name against a pattern, and still checks for `.`, `..`, `@{`, `\/` and names ending in `.lock`.\n\n**Why**\n\nThis check now accepts some branch names it used to reject.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}