New hook: check-moved-repos
See original GitHub issueI keep on finding pre-commit configs in various projects which are pointed at https://gitlab.com/pycqa/flake8
It would be awesome if I could turn on a hook which checks for hooks from that repo and flags them as needing an update to the github repo. The same holds for many repos like black
which have moved/renamed, and which only work because of github redirects.
I don’t know if this is a common case other than flake8, or if it’s so common that such a hook would be a huge pain to maintain. But it just needs to be able to read the pre-commit config and pull out the repos, not the rest of the config. It can skip support for old configs (top-level list) and make other simplifying assumptions as necessary.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Ultima™ Hook | Self-Ligation | Ormco Products
The Ultima Hooks are snap-fit hooks that also work as a stop.* They are the only repositionable, clippable hook that can be used...
Read more >Ultima Hook Launched by Ormco - Dentistry Today
Ormco Corporation has launched Ultima Hook, the first and only repositionable hook developed specifically for the Ultima wire.
Read more >Find a way to bootstrap Consul ACL support - IssueHint
New hook : check-moved-repos, 9, 2022-02-04, 2022-11-19. obj.instance_eval("SomeStrings") is not handled correctly, 1, 2021-03-18, 2022-11-18.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yeah I kinda wrote that off here – the hook config is a top-level list so there isn’t a good place to put it https://github.com/pre-commit/pre-commit/issues/2003#issuecomment-895186179
I’m going to close this 👍
I don’t really want to introduce
pre-commit.com
orpre-commit.ci
as a critical-path component for pre-commit’s operation – part of the current design is it’s entirely “distributed” and doesn’t have any phone-home