chore: lint PR titles/commit messages in the CI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 323
- Forks
- 133
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 2
Description
After #285 releases are now made using release-please. This however depends on enforcing conventional-commits on everything that lands on the main branch. For PRs this means linting both commit messages as well as the PR title - https://github.community/t/how-to-change-the-default-squash-merge-commit-message/1155. It would probably be a good idea to have an action validating this 👍
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's GitHub Actions workflows and reviewing how release-please consumes conventional-commits. Check the linked GitHub Community discussion for the PR title and squash-merge constraints. Done means CI validates both PR titles and commit messages before changes can land on main.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100