Repository navigation
ci: drop the PR title length cap and the banned-words gate - #3573
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Part of the 2026-10-19 process simplification. The PR title job keeps the format check and stops gating on title length and wording.
Change
check-pr-title.pykeeps the type, scope and!rules and drops the length limit.pr-title.ymlno longer runscheck-banned-words.sh. The script, its--stagedmode andscripts/banned-words.txtstay for local use and the docs repo.AGENTS.md,linux/AGENTS.md,linux/CONTRIBUTING.md, the PR template and.claude/rules/ci.mdno longer state the cap or the CI scan. The writing rule stays as guidance.Verified
test_check_pr_title.pypasses. The length cases in it are removed, since they pinned the cap this PR drops.pr-title.yml, andverify.sh agent-docspasses.