Skip to content

Pre-commit auto-update#19311

Merged
SaschaCowley merged 2 commits intomasterfrom
pre-commit-ci-update-config
Jan 28, 2026
Merged

Pre-commit auto-update#19311
SaschaCowley merged 2 commits intomasterfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Dec 1, 2025

@pre-commit-ci pre-commit-ci bot requested a review from a team as a code owner December 1, 2025 21:00
@pre-commit-ci pre-commit-ci bot requested a review from SaschaCowley December 1, 2025 21:00
@seanbudd seanbudd added the conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review. label Dec 4, 2025
updates:
- [github.com/astral-sh/ruff-pre-commit: v0.14.5 → v0.14.10](astral-sh/ruff-pre-commit@v0.14.5...v0.14.10)
- [github.com/astral-sh/uv-pre-commit: 0.9.11 → 0.9.21](astral-sh/uv-pre-commit@0.9.11...0.9.21)
- [github.com/DavidAnson/markdownlint-cli2: v0.18.1 → v0.20.0](DavidAnson/markdownlint-cli2@v0.18.1...v0.20.0)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 9b88052 to 952ae8f Compare January 5, 2026 20:40
@SaschaCowley SaschaCowley enabled auto-merge (squash) January 28, 2026 03:26
@SaschaCowley SaschaCowley merged commit 58033ba into master Jan 28, 2026
78 of 81 checks passed
@SaschaCowley SaschaCowley deleted the pre-commit-ci-update-config branch January 28, 2026 04:34
@github-actions github-actions bot added this to the 2026.2 milestone Jan 28, 2026
Comment on lines +322 to +325
"uv==0.9.27",
]
lint = [
"ruff==0.14.5",
"ruff==0.14.14",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SaschaCowley - please make sure to update changes for developers in changes.md

@seanbudd
Copy link
Member

@SaschaCowley - this shouldn't have been merged, it introduced a tonne of linting errors with new markdown rules. Now precommit is failing on master and all PRs based on master https://results.pre-commit.ci/run/github/45885732/1769574878.GcVUsVfhSo2kLzR9V4iI_g

seanbudd added a commit that referenced this pull request Jan 28, 2026
@seanbudd
Copy link
Member

Opened: #19522

seanbudd added a commit that referenced this pull request Jan 28, 2026
### Reverts PR
Reverts #19311
### Issues fixed
N/A

### Issues reopened
N/a
### Reason for revert

Introduced linting errors, forgot to update changes.md

### Can this PR be reimplemented? If so, what is required for the next
attempt
Linting errors need to be fixed
@SaschaCowley
Copy link
Member

@seanbudd pre-commit CI is kind of useless if it failing doesn't count as checks failing

@seanbudd
Copy link
Member

@SaschaCowley - the commit you merged had a failing check: a1497b9. We just don't have branch protection rules set up for it. I'll ad them now

@SaschaCowley
Copy link
Member

@SaschaCowley - the commit you merged had a failing check: a1497b9. We just don't have branch protection rules set up for it. I'll ad them now

Thanks. I am (now) aware that it had a failing check, but we either need to have all required checks required in branch protection rules, or disable the merge queue. Disabling the merge queue doesn't fully solve the problem anyway, because GitHub would still happily let you merge manually with failing checks - which aren't necessarily obvious when using a screen reader or GitHub CLI.

@seanbudd
Copy link
Member

Branch protection rules is where you define the required checks. I believe pre-commit was there before but it was possibly missed when setting it up. either way, it is there now as a required check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants