#precommit — Public Fediverse posts

prek now supports cooldown in either user or project config:

https://github.com/j178/prek/releases/tag/v0.3.12

pre-commit closed and locked the feature request as one of many many duplicates, but I can't find any:

https://github.com/pre-commit/pre-commit/issues/3614

#PreCommit #prek #cooldown

prek now supports cooldown in either user or project config:

https://github.com/j178/prek/releases/tag/v0.3.12

pre-commit closed and locked the feature request as one of many many duplicates, but I can't find any:

https://github.com/pre-commit/pre-commit/issues/3614

#PreCommit #prek #cooldown

prek now supports cooldown in either user or project config:

https://github.com/j178/prek/releases/tag/v0.3.12

pre-commit closed and locked the feature request as one of many many duplicates, but I can't find any:

https://github.com/pre-commit/pre-commit/issues/3614

#PreCommit #prek #cooldown

prek now supports cooldown in either user or project config:

https://github.com/j178/prek/releases/tag/v0.3.12

pre-commit closed and locked the feature request as one of many many duplicates, but I can't find any:

https://github.com/pre-commit/pre-commit/issues/3614

#PreCommit #prek #cooldown

prek now supports cooldown in either user or project config:

https://github.com/j178/prek/releases/tag/v0.3.12

pre-commit closed and locked the feature request as one of many many duplicates, but I can't find any:

https://github.com/pre-commit/pre-commit/issues/3614

#PreCommit #prek #cooldown

To aid #developers using #AI to disclose their prompts and make the #collaboration more obvious, we maintain a simple #tool that allows developers to collect all prompts and append them to commit messages:

https://github.com/pycalendar/ai-prompt-auto-commit

Projects using #Claude_code or #GitHubCopilot can automate the commit workflow using a #precommit #hook.

#generativeAI #pycal

To aid #developers using #AI to disclose their prompts and make the #collaboration more obvious, we maintain a simple #tool that allows developers to collect all prompts and append them to commit messages:

https://github.com/pycalendar/ai-prompt-auto-commit

Projects using #Claude_code or #GitHubCopilot can automate the commit workflow using a #precommit #hook.

#generativeAI #pycal

To aid #developers using #AI to disclose their prompts and make the #collaboration more obvious, we maintain a simple #tool that allows developers to collect all prompts and append them to commit messages:

https://github.com/pycalendar/ai-prompt-auto-commit

Projects using #Claude_code or #GitHubCopilot can automate the commit workflow using a #precommit #hook.

#generativeAI #pycal

I wanted to talk even more about dockerizing pre-commit for security gains - so I typed up a short blog post about how to achieve this.

Please feel invited to try it out and share back results ⬇️

https://overtag.dk/v2/blog/pre-commit-in-docker/

I'd also like to hear from people who aren't worried about pre-commit vulnerabilities and why ❓

#precommit #python

I wanted to talk even more about dockerizing pre-commit for security gains - so I typed up a short blog post about how to achieve this.

Please feel invited to try it out and share back results ⬇️

https://overtag.dk/v2/blog/pre-commit-in-docker/

I'd also like to hear from people who aren't worried about pre-commit vulnerabilities and why ❓

#precommit #python

I wanted to talk even more about dockerizing pre-commit for security gains - so I typed up a short blog post about how to achieve this.

Please feel invited to try it out and share back results ⬇️

https://overtag.dk/v2/blog/pre-commit-in-docker/

I'd also like to hear from people who aren't worried about pre-commit vulnerabilities and why ❓

#precommit #python

I wanted to talk even more about dockerizing pre-commit for security gains - so I typed up a short blog post about how to achieve this.

Please feel invited to try it out and share back results ⬇️

https://overtag.dk/v2/blog/pre-commit-in-docker/

I'd also like to hear from people who aren't worried about pre-commit vulnerabilities and why ❓

#precommit #python

I wanted to talk even more about dockerizing pre-commit for security gains - so I typed up a short blog post about how to achieve this.

Please feel invited to try it out and share back results ⬇️

https://overtag.dk/v2/blog/pre-commit-in-docker/

I'd also like to hear from people who aren't worried about pre-commit vulnerabilities and why ❓

#precommit #python

A screenshot from running a dockerized pre-commit.

And here's the whole darn alias 🥳

```
$ which pre-commit
pre-commit: aliased to docker run -v "pre-commit-cache":/home/dockeruser/.cache -v "$(pwd)":/repo:rw -e PRECOMMITALIAS="$(alias pre-commit)" -e PGID="$(id -g)" -e PUID="$(id -u)" pre-commit:python3.14
```

Instructions on building and running it are in the repo ⬇️
https://codeberg.org/benjaoming/pre-commit-docker-alias

#precommit

A screenshot from running a dockerized pre-commit.

And here's the whole darn alias 🥳

```
$ which pre-commit
pre-commit: aliased to docker run -v "pre-commit-cache":/home/dockeruser/.cache -v "$(pwd)":/repo:rw -e PRECOMMITALIAS="$(alias pre-commit)" -e PGID="$(id -g)" -e PUID="$(id -u)" pre-commit:python3.14
```

Instructions on building and running it are in the repo ⬇️
https://codeberg.org/benjaoming/pre-commit-docker-alias

#precommit

A screenshot from running a dockerized pre-commit.

And here's the whole darn alias 🥳

```
$ which pre-commit
pre-commit: aliased to docker run -v "pre-commit-cache":/home/dockeruser/.cache -v "$(pwd)":/repo:rw -e PRECOMMITALIAS="$(alias pre-commit)" -e PGID="$(id -g)" -e PUID="$(id -u)" pre-commit:python3.14
```

Instructions on building and running it are in the repo ⬇️
https://codeberg.org/benjaoming/pre-commit-docker-alias

#precommit

A screenshot from running a dockerized pre-commit.

And here's the whole darn alias 🥳

```
$ which pre-commit
pre-commit: aliased to docker run -v "pre-commit-cache":/home/dockeruser/.cache -v "$(pwd)":/repo:rw -e PRECOMMITALIAS="$(alias pre-commit)" -e PGID="$(id -g)" -e PUID="$(id -u)" pre-commit:python3.14
```

Instructions on building and running it are in the repo ⬇️
https://codeberg.org/benjaoming/pre-commit-docker-alias

#precommit

A screenshot from running a dockerized pre-commit.

And here's the whole darn alias 🥳

```
$ which pre-commit
pre-commit: aliased to docker run -v "pre-commit-cache":/home/dockeruser/.cache -v "$(pwd)":/repo:rw -e PRECOMMITALIAS="$(alias pre-commit)" -e PGID="$(id -g)" -e PUID="$(id -u)" pre-commit:python3.14
```

Instructions on building and running it are in the repo ⬇️
https://codeberg.org/benjaoming/pre-commit-docker-alias

#precommit

Was contemplating if it makes sense to have a single image for ALL pre-commit needs and alias `pre-commit` to `docker run pre-commit -v "$(pwd)":/workdir:rw`

Oh and yes, this is inspired by all the supply chain stuff. If the alternative is that each pre-commit hook becomes its own Docker image, I'm afraid it'll be too slow.

Any experiences?

(edited: docker exec isn't possible with volumes)

#precommit

Was contemplating if it makes sense to have a single image for ALL pre-commit needs and alias `pre-commit` to `docker run pre-commit -v "$(pwd)":/workdir:rw`

Oh and yes, this is inspired by all the supply chain stuff. If the alternative is that each pre-commit hook becomes its own Docker image, I'm afraid it'll be too slow.

Any experiences?

(edited: docker exec isn't possible with volumes)

#precommit

Was contemplating if it makes sense to have a single image for ALL pre-commit needs and alias `pre-commit` to `docker run pre-commit -v "$(pwd)":/workdir:rw`

Oh and yes, this is inspired by all the supply chain stuff. If the alternative is that each pre-commit hook becomes its own Docker image, I'm afraid it'll be too slow.

Any experiences?

(edited: docker exec isn't possible with volumes)

#precommit

Was contemplating if it makes sense to have a single image for ALL pre-commit needs and alias `pre-commit` to `docker run pre-commit -v "$(pwd)":/workdir:rw`

Oh and yes, this is inspired by all the supply chain stuff. If the alternative is that each pre-commit hook becomes its own Docker image, I'm afraid it'll be too slow.

Any experiences?

(edited: docker exec isn't possible with volumes)

#precommit

Was contemplating if it makes sense to have a single image for ALL pre-commit needs and alias `pre-commit` to `docker run pre-commit -v "$(pwd)":/workdir:rw`

Oh and yes, this is inspired by all the supply chain stuff. If the alternative is that each pre-commit hook becomes its own Docker image, I'm afraid it'll be too slow.

Any experiences?

(edited: docker exec isn't possible with volumes)

#precommit

My plan B is to look at running #PreCommit alternative #Prek https://prek.j178.dev/ on #Codeberg’s Woodpecker CI (where quicker installation and faster runtimes etc should pay off)

My plan B is to look at running #PreCommit alternative #Prek https://prek.j178.dev/ on #Codeberg’s Woodpecker CI (where quicker installation and faster runtimes etc should pay off)

My plan B is to look at running #PreCommit alternative #Prek https://prek.j178.dev/ on #Codeberg’s Woodpecker CI (where quicker installation and faster runtimes etc should pay off)

My plan B is to look at running #PreCommit alternative #Prek https://prek.j178.dev/ on #Codeberg’s Woodpecker CI (where quicker installation and faster runtimes etc should pay off)

My plan B is to look at running #PreCommit alternative #Prek https://prek.j178.dev/ on #Codeberg’s Woodpecker CI (where quicker installation and faster runtimes etc should pay off)

Running the #PreCommit tool (for listing, enforcing coding style, etc) via the author’s CI service https://pre-commit.ci/ has excellent #GitHub integration - with the docs suggesting that other hosting sites might be supported at some point.

I’ve just asked directly about #Codeberg (and #ForgeJo generally) as I’d love to use it there too: https://github.com/pre-commit-ci/issues/issues/261

Running the #PreCommit tool (for listing, enforcing coding style, etc) via the author’s CI service https://pre-commit.ci/ has excellent #GitHub integration - with the docs suggesting that other hosting sites might be supported at some point.

I’ve just asked directly about #Codeberg (and #ForgeJo generally) as I’d love to use it there too: https://github.com/pre-commit-ci/issues/issues/261

Running the #PreCommit tool (for listing, enforcing coding style, etc) via the author’s CI service https://pre-commit.ci/ has excellent #GitHub integration - with the docs suggesting that other hosting sites might be supported at some point.

I’ve just asked directly about #Codeberg (and #ForgeJo generally) as I’d love to use it there too: https://github.com/pre-commit-ci/issues/issues/261

Running the #PreCommit tool (for listing, enforcing coding style, etc) via the author’s CI service https://pre-commit.ci/ has excellent #GitHub integration - with the docs suggesting that other hosting sites might be supported at some point.

I’ve just asked directly about #Codeberg (and #ForgeJo generally) as I’d love to use it there too: https://github.com/pre-commit-ci/issues/issues/261

Running the #PreCommit tool (for listing, enforcing coding style, etc) via the author’s CI service https://pre-commit.ci/ has excellent #GitHub integration - with the docs suggesting that other hosting sites might be supported at some point.

I’ve just asked directly about #Codeberg (and #ForgeJo generally) as I’d love to use it there too: https://github.com/pre-commit-ci/issues/issues/261

At work we maintain a range of project templates for various languages such as #Python and #cpp we have been looking to migrate from #tox to #precommit and #uv but now #Astral the company behind uv and ruff has been acquired by OpenAI.

So everything is ready im just not sure anymore if we should, despite certain benefits its quite hard to ignore how many things are being ruined by corporate AI

If you are wondering about such a pre-commit + uv setup you can find it here: https://github.com/astron-rd/PACE/pull/50

At work we maintain a range of project templates for various languages such as #Python and #cpp we have been looking to migrate from #tox to #precommit and #uv but now #Astral the company behind uv and ruff has been acquired by OpenAI.

So everything is ready im just not sure anymore if we should, despite certain benefits its quite hard to ignore how many things are being ruined by corporate AI

If you are wondering about such a pre-commit + uv setup you can find it here: https://github.com/astron-rd/PACE/pull/50

At work we maintain a range of project templates for various languages such as #Python and #cpp we have been looking to migrate from #tox to #precommit and #uv but now #Astral the company behind uv and ruff has been acquired by OpenAI.

So everything is ready im just not sure anymore if we should, despite certain benefits its quite hard to ignore how many things are being ruined by corporate AI

If you are wondering about such a pre-commit + uv setup you can find it here: https://github.com/astron-rd/PACE/pull/50

At work we maintain a range of project templates for various languages such as #Python and #cpp we have been looking to migrate from #tox to #precommit and #uv but now #Astral the company behind uv and ruff has been acquired by OpenAI.

So everything is ready im just not sure anymore if we should, despite certain benefits its quite hard to ignore how many things are being ruined by corporate AI

If you are wondering about such a pre-commit + uv setup you can find it here: https://github.com/astron-rd/PACE/pull/50

Investigating the conversion between #tox and #pip enabled projects to #precommit and #UV

This investigation is almost done and will modernize our #cruft #cookiecutter Python template.

Investigating the conversion between #tox and #pip enabled projects to #precommit and #UV

This investigation is almost done and will modernize our #cruft #cookiecutter Python template.

Investigating the conversion between #tox and #pip enabled projects to #precommit and #UV

This investigation is almost done and will modernize our #cruft #cookiecutter Python template.

Investigating the conversion between #tox and #pip enabled projects to #precommit and #UV

This investigation is almost done and will modernize our #cruft #cookiecutter Python template.

I have a simple script that adds and updates dates in a blog post by prek (precommit) before git commit.

It works well in linux, but does not work as expected on macos. In Mac it sets initial time, but does not update it.

I thought it’s very simple bug, very good to delegate to AI coding tool, my AI agent was github copilot.

Copilot generated me nodejs code inside bash to fix the issue, but it did not. It rewrote almost completely my bash script to nodejs, but it did not work as well.

When I gave up and checked by myself, it required to add “-u” option to “date” cli for macOS.

There was an another task that involved another git command’s parameters and “AI” decided to add 20 lines of code with no positive result.

How do people build a startup and fully functional apps with it?

I use it for function generations, tests, structs… but when it goes to something more complicated it never works with “good enough” quality for me.

#prek #precommit #linux #macos #ai #github #github_Copilot #bash #nodejs #startup #git

I have a simple script that adds and updates dates in a blog post by prek (precommit) before git commit.

It works well in linux, but does not work as expected on macos. In Mac it sets initial time, but does not update it.

I thought it’s very simple bug, very good to delegate to AI coding tool, my AI agent was github copilot.

Copilot generated me nodejs code inside bash to fix the issue, but it did not. It rewrote almost completely my bash script to nodejs, but it did not work as well.

When I gave up and checked by myself, it required to add “-u” option to “date” cli for macOS.

There was an another task that involved another git command’s parameters and “AI” decided to add 20 lines of code with no positive result.

How do people build a startup and fully functional apps with it?

I use it for function generations, tests, structs… but when it goes to something more complicated it never works with “good enough” quality for me.

#prek #precommit #linux #macos #ai #github #github_Copilot #bash #nodejs #startup #git

I have a simple script that adds and updates dates in a blog post by prek (precommit) before git commit.

It works well in linux, but does not work as expected on macos. In Mac it sets initial time, but does not update it.

I thought it’s very simple bug, very good to delegate to AI coding tool, my AI agent was github copilot.

Copilot generated me nodejs code inside bash to fix the issue, but it did not. It rewrote almost completely my bash script to nodejs, but it did not work as well.

When I gave up and checked by myself, it required to add “-u” option to “date” cli for macOS.

There was an another task that involved another git command’s parameters and “AI” decided to add 20 lines of code with no positive result.

How do people build a startup and fully functional apps with it?

I use it for function generations, tests, structs… but when it goes to something more complicated it never works with “good enough” quality for me.

#prek #precommit #linux #macos #ai #github #github_Copilot #bash #nodejs #startup #git

I have a simple script that adds and updates dates in a blog post by prek (precommit) before git commit.

It works well in linux, but does not work as expected on macos. In Mac it sets initial time, but does not update it.

I thought it’s very simple bug, very good to delegate to AI coding tool, my AI agent was github copilot.

Copilot generated me nodejs code inside bash to fix the issue, but it did not. It rewrote almost completely my bash script to nodejs, but it did not work as well.

When I gave up and checked by myself, it required to add “-u” option to “date” cli for macOS.

There was an another task that involved another git command’s parameters and “AI” decided to add 20 lines of code with no positive result.

How do people build a startup and fully functional apps with it?

I use it for function generations, tests, structs… but when it goes to something more complicated it never works with “good enough” quality for me.

#prek #precommit #linux #macos #ai #github #github_Copilot #bash #nodejs #startup #git

I have a simple script that adds and updates dates in a blog post by prek (precommit) before git commit.

It works well in linux, but does not work as expected on macos. In Mac it sets initial time, but does not update it.

I thought it’s very simple bug, very good to delegate to AI coding tool, my AI agent was github copilot.

Copilot generated me nodejs code inside bash to fix the issue, but it did not. It rewrote almost completely my bash script to nodejs, but it did not work as well.

When I gave up and checked by myself, it required to add “-u” option to “date” cli for macOS.

There was an another task that involved another git command’s parameters and “AI” decided to add 20 lines of code with no positive result.

How do people build a startup and fully functional apps with it?

I use it for function generations, tests, structs… but when it goes to something more complicated it never works with “good enough” quality for me.

#prek #precommit #linux #macos #ai #github #github_Copilot #bash #nodejs #startup #git

Not my post but worth reading...

pre-commit hooks are fundamentally broken

https://jyn.dev/pre-commit-hooks-are-fundamentally-broken/

Note that the pre-commit framework can also be used to manage pre-push and other hooks

#git #precommit #hooks

Not my post but worth reading...

pre-commit hooks are fundamentally broken

https://jyn.dev/pre-commit-hooks-are-fundamentally-broken/

Note that the pre-commit framework can also be used to manage pre-push and other hooks

#git #precommit #hooks

Not my post but worth reading...

pre-commit hooks are fundamentally broken

https://jyn.dev/pre-commit-hooks-are-fundamentally-broken/

Note that the pre-commit framework can also be used to manage pre-push and other hooks

#git #precommit #hooks

My day job is all about #Python (which I love). Here are some personal rules, specific to working with Python projects:

* Do **not** install or modify global tools, especially Python itself or any packages. This means a given system might not even **have** a global Python
* Always use virtual environments (`uv` agrees with me, and doesn't need this but). I always set the global environment variable `PIP_REQUIRE_VIRTUALENV`.
* The two rules above mean my virtual environment contains (not via a link, it's really there) Python itself (and of course, of the right version)
* Virtual environments always live **inside** a project directory. Never global.
* Activate virtual environments only **inside** the project directory (`direnv` #direnv makes this easy)
* Don't install (let alone use) #Anaconda, #Miniconda, or #Mamba, because those violate all the rules above (but see the next rule)
* Anaconda-based packages implies a `pixi` #Pixi project (it's the same people, but a better answer, and you still get what you want -- the correct packages)
* No Anaconda-based packages implies a `uv` #UV project
* Always use `pyproject.toml` #pyprojecttoml over any other config file (e.g., `requirements.txt` #requirementstxt), except where things just don't work, such as needing `pyrefly.toml`
* `uv`, `pixi`, and `direnv` must exist outside of any project, so install them at the user level, or else globally if and only if that is appropriate and compelling enough to override rule one

That was a wall of text, but in practice doing it this way is trivial. It's probably **less** work than you have been doing. This post is just about managing your Python versions, environments, and projects. Not about, e.g., using `pre-commit` #precommit, or doing type checking, etc. But if you follow these rules, your work will be easier, faster, more adaptable, and encounter fewer obstacles.

#HowTo