You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project would benefit from a PR title checker that ensures conformity to conventional commit prefixes. Currently, the following prefixes are considered valid:
build:
chore:
docs:
feat:
fix:
perf:
refactor:
revert:
style:
test:
Problem:
Enforcing consistent and descriptive PR titles following conventional commit prefixes helps maintain clarity and organization in the project's version history.
Solution:
Implement a PR title checker that validates each PR title against the specified conventional commit prefixes. This will ensure that PR titles adhere to the established guidelines.
To-Do:
Develop the PR title checker script to verify titles against the defined prefixes.
Integrate the checker into the project's CI/CD pipeline.
Define error messages or warnings for non-compliant PR titles.
Priority/Impact
Medium
Checklist
I have read the Contributing Guidelines
I am willing to work on this issue
I am a WOC 4.0 contributor
The text was updated successfully, but these errors were encountered:
Hi there! Thanks for opening this issue @harmeetsingh11!. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.If belong's to SWOC program role ur self as Contributor in OS lead site Link : https://www.oslead.xyz/usertype , so that ur points will be assigned to the leaderboard. New to Open Source Contribution check out the below YT video , Happy Coding🚀💻🐛 🔗 Link : https://www.youtube.com/watch?v=3afUKB3guZA
…fixes (#889)
## Related Issues
- Closes#883
## Description
This pull request addresses the need for a PR title checker to ensure
conformity to conventional commit prefixes. The specified prefixes
include `build`, `chore`, `docs`, `feat`, `fix`, `perf`, `refactor`,
`revert`, `style`, and `test`. Consistent PR titles are essential for
maintaining clarity and organization in the project's version history.
### Files added
- `.github/pr-title-checker.json`
- `.github/workflows/pr-title-checker.yml`
### Solution:
1. Developed a PR title checker script to validate titles against the
defined prefixes.
2. Integrated the checker into the project's CI/CD pipeline for
automatic validation.
3. Defined clear error messages for non-compliant PR titles, aiding
contributors in adhering to guidelines.
### To-Do:
- [x] Develop and test the PR title checker script.
- [x] Integrate the checker into the CI/CD pipeline.
- [x] Define error messages for non-compliant PR titles.
This PR enhances the project's contribution guidelines by automating the
validation of PR titles, ensuring adherence to conventional commit
prefixes. Contributions and feedback are encouraged for continuous
improvement.
## Checklist
<!-- [X] - put a cross/X inside [] to check the box -->
- [X] I have gone through the [contributing
guide](https://github.com/Anjaliavv51/Retro)
- [X] I have updated my branch and synced it with project `main` branch
before making this PR
- [X] I have performed a self-review of my code
- [X] I have tested the changes thoroughly before submitting this pull
request.
- [X] I have provided relevant issue numbers, screenshots, and videos
after making the changes.
Is there an existing feature request for this?
Description:
The project would benefit from a PR title checker that ensures conformity to conventional commit prefixes. Currently, the following prefixes are considered valid:
build:
chore:
docs:
feat:
fix:
perf:
refactor:
revert:
style:
test:
Problem:
Enforcing consistent and descriptive PR titles following conventional commit prefixes helps maintain clarity and organization in the project's version history.
Solution:
Implement a PR title checker that validates each PR title against the specified conventional commit prefixes. This will ensure that PR titles adhere to the established guidelines.
To-Do:
Priority/Impact
Medium
Checklist
The text was updated successfully, but these errors were encountered: