#51729: build: add remaining checks to Chromium roll message linting
Description of Change
This buttons up the remaining linting checks:
chore: update patchesmust have no commit body and only only non-content patch changes- A commit referencing a single CL must use
<CL_NUMBER>: <upstream CL's original title>as the first line of the commit message - A commit referencing multiple CLs can have whatever commit message it would like
This also enforces that all commits meet our existing patterns. As always, Skip-Lint: <reason> can be used to skip linting any given commit.
I also tasked Claude with updating the Chromium upgrade skill to ensure compliance with these linting rules. For now I've disabled the non-zero exit code locally, so that we can let this get some mileage and ensure Claude is complying before always enforcing it.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron