gitlint
gitlint copied to clipboard
jorisroovers
Linting for your git commit messages
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 4 to 5. Release notes Sourced from docker/build-push-action's releases. v5.0.0 Node 20 as default runtime (requires Actions Runner v2.308.0 or later) by @crazy-max in docker/build-push-action#954 Bump @actions/core...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4. Release notes Sourced from actions/checkout's releases. v4.0.0 What's Changed Update default runtime to node20 by @takost in actions/checkout#1436 Support fetching without the --progress option...
While evalulating the use of `gitlint` I was pretty impressed by the configurability and ease of creating your own linting rules. Thanks a lot for creating and maintaining this tool!...
To consider as part of this: - [ ] Ensure publishing secrets aren't available to CI jobs - [x] Consider adding branch protection rules - [ ] Add permissions: https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs...
Mostly involves fixing the hook tests.
Hi, _gitlint_ is not able to detect a commit message that starts with a hash sign. A commit message can begin with a hash sign (for example, by using the...
It would be really helpful if gitlint would optionally generate a junit or [SARIF](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) report. It acts like any other static analysis report.
One of the nice things of [nox](https://nox.thea.codes) are good defaults, no matter if it's run in CI or not. I thought it'd make sense for gitlint, too. Following the [nox...
This is not a bug in `gitlint` itself, but a problem caused by interaction with `pre-commit`: running `pre-commit autoupdate` updates `gitlint` hook in `.pre-commit-config.yaml` to `v0.19.0dev`. This is not good...
This issue will be used to track any overarching discussion and work related to `0.20.0`. # Scope **As always, everything discussed in this issue is subject to sudden change at...