reLint 3.5 is out!
Special thanks to @BatmanAoD

https://github.com/codingjoe/relint

#python #javascript #openSource #regex #linter #precommit #skills

RE: https://hachyderm.io/@cleder/116823890089323460

#prek and #precommit go #🦧️💩️ over insecure code produced by #AI #LLM
- would have been the clickbaity headline 😁️ @calvin

An unexpected bonus when you generate your `pre-commit-config.yaml` with `ps-init --detect` is that from the installed hooks: detect-secrets, proselint, codespell, commitizen, typos, cargo-check, clippy, fmt, gitleaks, yamlfmt, gitlint, pre-commit-sort, ryl, rumdl-fmt, semgrep, doctoc, talisman-commit, trufflehog, zizmor

That when prompted "create github actions including unittests (with coverage)", agents write for e.g. a fresh #rust project

```
.github/workflows
├── ci.yml
├── compat.yml
├── lint.yml
├── release.yml
└── security.yml
```

and configure all the lint and security github actions -- which in turn will make the commit go 🐒 💩 , the security hooks reporting a lot of 'concerns' about the insecure configuration the LLM wrote, resulting in a feedback loop to harden them ;-)

#prek #precommit #python
@pythonbytes @calvinhp
https://github.com/cleder/gpc-init/

You’re starting a new project, you’ve got your repo initialized, and now comes the tedious part—setting up the quality gates.

You know you need pre-commit (or the newer #prek to keep your code clean, but you end up hunting through your older repositories to find the "best" `.pre-commit-config.yaml` to copy and paste.

It’s a chore that breaks your flow before you’ve even written a line of code.

@pythonbytes @mkennedy @calvinhp
#precommit
https://github.com/cleder/gpc-init

RE: https://hachyderm.io/@cleder/116807441810538608

The #awesomelist for the #awesome #precommit and #prek are now at 58 unique repos.

Languages: docker, go, img, js, md, nb, py, r, ru, sh, sql, tf, toml, ts, yaml

Frameworks: Django, git, k8s, react, sphinx

Thank you ❣️

https://github.com/cleder/awesome-pre-commit-hooks

RE: https://hachyderm.io/@cleder/116796446972749174

My #awesomelist for #precommit and #prek is now at 60 #awesome hooks. 🎉

Find linters, formatters, security scanners, code quality tools, and more in one place.

Contributions welcome! 🔧

Languages

docker, go, img, js, md, nb, py, ru, sh, sql, tf, toml, ts, yaml

Frameworks

bevy, django, git, k8s, react, sphinx

⭐ https://github.com/cleder/awesome-pre-commit-hooks

#Python #DevOps #OpenSource #DeveloperTools #CodeQuality

The pre-commit ecosystem is huge, but discovering good hooks can be surprisingly difficult.

I've started **Awesome Pre-commit Hooks**, a curated list of #precommit and #prek hooks organised by language and framework.

Check it out and help grow it:

https://github.com/cleder/awesome-pre-commit-hooks

#Python #OpenSource #DevTools #CodeQuality #Automation

I use pre-commit (and now are beginning to migrate to prek) extensively in all my projects (work and hobby), and create a lot of repositories (every other month or so, enough for this to be a pain point, but not enough to have the workflow committed to my muscle memory).

Whenever I created a new repo, I had to cut and paste the .pre-commit-config.yaml into the new project, which requires remembering what other project has the most appropriate and up-to-date configuration.

Now I ditched the Copy-Paste Workflow: Scaffold Your Quality Tools with pc-init

#python #prek #precommit

https://dev.to/ldrscke/stop-copying-your-pre-commit-configyaml-241d