nodejs / nodejs/node-core-utils
Update workflow to check for conventional commit types
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
I recommend updating the pull request workflow to check for conventional commit format in the commits, since release changelog requires it.
If there's no objections, I'll be happy to add it.
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 pull request workflow and reviewing how commits are currently validated. Read the Conventional Commits specification linked in the issue, then determine the repository's release changelog requirements. Done means the workflow rejects commits with invalid types and accepts valid conventional commit messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100