ci: migrate commit validation to prek+gitlint and standardize CI tool setup - #28
Merged
Merged
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3f5e002134
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
… setup Replace Node/commitlint-based commit checks with prek+gitlint and add a mise task for CI commit-range validation. Standardize GitHub workflows on mise-managed tool installation, add PYTHON_VERSION-driven Python/uv setup, and remove obsolete Node commitlint artifacts. Update contributor/agent docs to reflect gitlint CT1 and commit body line-length constraints.
datenzar
force-pushed
the
ci/migrate-commit-checks-to-prek-gitlint
branch
from
March 8, 2026 22:05
3f5e002 to
e3e7633
Compare
Run the GitHub Actions commit-range checks through uvx so they do not depend on syncing the macOS-only project environment. Keep local mise and prek commands on uv run so developer hooks still use the repository-managed dev environment.
Keep conventional title validation in CI while matching the repository's existing commit style, which often uses subject-only messages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
prek+gitlintmise-managed Python/uv setupuv.lockand publish artifacts through the existing build/test/release flowWhat Changed
prek/gitlintuvviamiseinstead of mixed setup paths.github/workflows/release.ymlso release jobs:uv.lockfor the semantic-release version commitWhy
The repo was carrying overlapping tooling for commit validation and environment setup. This change reduces maintenance overhead, keeps local/CI behavior aligned, and makes the release pipeline more reproducible by ensuring the lockfile and build artifacts are handled consistently.
Testing
CONTRIBUTING.mdand enforced gitlint conventions