public issues for https://pre-commit.ci
active 2024-05-27 → 2026-04-10 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 684 days from 2024-05-27 to 2026-04-10. Pushes: 0 total, peak 0 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 33 total, peak 3 in a day. Comments: 53 total, peak 5 in a day. Stars: 3 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| asottile | 54 | 0 | 0 | 37 |
| Samuel-Therrien-Beslogic | 3 | 0 | 0 | 1 |
| alyssadai | 2 | 0 | 0 | 2 |
| seanbudd | 2 | 0 | 0 | 1 |
| adnathanail | 2 | 0 | 0 | 2 |
| cdwilson | 2 | 0 | 0 | 1 |
| Peiffap | 2 | 0 | 0 | 1 |
| chrishavlin | 2 | 0 | 0 | 1 |
| vkucera | 2 | 0 | 0 | 2 |
| rkm | 2 | 0 | 0 | 1 |
| djmitche | 2 | 0 | 0 | 1 |
| mxr | 2 | 0 | 0 | 1 |
| Borda | 1 | 0 | 0 | 1 |
| jakob1379 | 1 | 0 | 0 | 0 |
| zaro0508 | 1 | 0 | 0 | 0 |
| pathum2583-eng | 1 | 0 | 1 | 0 |
| paduszyk | 1 | 0 | 0 | 0 |
| vivodi | 1 | 0 | 0 | 0 |
| Freed-Wu | 1 | 0 | 0 | 0 |
| injust | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Pull request#264pathum2583-eng2026-04-10 03:52
- Issue comment#263asottile2026-04-09 11:41Can I specify triggers so that pre-commit.ci runs only on PRs or pushes to a named branch?
- Issue#258asottile2026-02-01 14:13Paid for Enterprise but repo still shows 'private repos require a paid plan
- Issue#260asottile2026-02-01 14:08Add support for prek builtin repo
- Issue comment#260asottile2026-02-01 14:08Add support for prek builtin repo
- Issue#259jakob13792026-01-25 15:43Add `ci.skip` or `ci.exclude` configuration for ci-specific file exclusions
- Issue comment#76Borda2025-11-13 18:50LFS support
- Issue#256avilaton2025-11-05 19:24Added uv-lock pre-commit hook and getting a failure only on pre-commit.ci
- Issue comment#255asottile2025-05-28 00:55npm install not running in CI
- Issue#255RayBB2025-05-28 00:51npm install not running in CI
- Issue comment#254asottile2025-05-17 12:42pre-commit.ci runs hooks on all files instead of only changed
- Issue comment#254vkucera2025-05-17 12:35pre-commit.ci runs hooks on all files instead of only changed
- Issue comment#244asottile2025-05-17 12:28In a PR pre-commit hooks are applied to all files
- Issue comment#244vkucera2025-05-17 12:25In a PR pre-commit hooks are applied to all files
- Issue comment#252asottile2025-04-09 00:44`mypy` giving false positive specifically on pre-commit.ci
- Issue comment#106adnathanail2025-03-27 01:50Running GitHub Actions only after pre-commit.ci suceeds to save resources, built time etc.
- Issue comment#106adnathanail2025-03-27 01:25Running GitHub Actions only after pre-commit.ci suceeds to save resources, built time etc.
- Issue comment#248asottile2025-03-15 17:20Support rust 2024 edition
- Issue#248asottile2025-03-15 17:20Support rust 2024 edition
- Issue comment#242mxr2025-01-26 19:54Messaging on skipped autofixes (due to bot pushes) is confusing
- Issue comment#242asottile2025-01-26 19:51Messaging on skipped autofixes (due to bot pushes) is confusing
- Issue#242asottile2025-01-26 19:51Messaging on skipped autofixes (due to bot pushes) is confusing
- Issue comment#242asottile2025-01-26 19:43Messaging on skipped autofixes (due to bot pushes) is confusing
- Issue#242mxr2025-01-26 19:28Messaging on skipped autofixes (due to bot pushes) is confusing
- Issue comment#241asottile2025-01-15 22:52pre-commit.ci runner fails when making API request
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 3 stars here means stars gained during the window, not the repo's star count.