David Culley

Hi @greatestview, your fix works fine on my machine. Thanks! Can you explain what exactly you did to the `.icns` file and how you did it?

> As far as I can tell, there's no reason _not_ to leave these as `commit`, `merge-commit` and `push` for now. Agreed. > the current version of pre-commit supports both...

> I think we should just revert #3940 , afaict users who care about specific stages can just specify that directly in their own config. Does that sound reasonable, @davidculley?...

> #4041 is the better solution, no? It's definitely a solution that requires no work on the side of the user (except for updating `black`, of course), whereas the more...

Does executing [`pre-commit clean`](https://pre-commit.com/#pre-commit-clean) fix the issue?

@Wolfcast: Your error message says `Expected […] commit` which hints at a version of `pre-commit` older than version 3.2.0 — since version 3.2.0, it's `pre-commit` instead of just `commit` —...

What am I missing @andrewmwilson @marcindulak, why can't Debian/Ubuntu users not execute `pip install --user pre-commit` to get a current version of `pre-commit`?

> In hobby projects it's possible to pull packages from the internet, but in enterprises someone with required permissions would need to modify CI systems and developer machine images to...

I have the same problem. @radoering The [Snowpark API](https://docs.snowflake.com/en/developer-guide/snowpark/index) of the cloud data warehouse [Snowflake](https://www.snowflake.com/en/) finally supports Python 3.11 since the [recently released version 1.9.0](https://github.com/snowflakedb/snowpark-python/releases/tag/v1.9.0) and I want to update...