Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: implement PR title checker workflow for conventional commit prefixes #71

Open
4 of 7 tasks
harmeetsingh11 opened this issue May 29, 2024 · 2 comments
Open
4 of 7 tasks

Comments

@harmeetsingh11
Copy link

Is your feature request related to a problem? Please describe.

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.

Describe the solution you'd like

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.

Screenshots

No response

Checklist

  • I have checked the existing issues
  • I have read the Contributing Guidelines
  • I am willing to work on this issue
  • I am a GSSoC'24 contributor
Copy link

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTION.md for guidelines on contributing to this project.

@TusharAMD
Copy link
Owner

Keep this on hold we need to decide whether to include and what level it should be assigned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants