-
Notifications
You must be signed in to change notification settings - Fork 15
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
ci: enforce semantic PRs; PR template #70
Conversation
Fixes #33 In addition to implementing the enforcement of semantic pull request titles, this update addresses the following configuration concerns within the project: Conflict Detection in Pull Requests: The system now checks for conflicts within pull requests, ensuring a smoother merging process. Improved Pull Request Template: The previous pull request template was excessively long and cumbersome, containing unnecessary elements. The new template has been streamlined to provide only essential information, simplifying the pull request creation process. fix #33
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, after changing the PR title, the workflow fails with a message that the scope is missing. It's a good test for how well this PR works :) However, I don't agree that a scope is necessary. A scope makes sense in big projects, or in the scope of the monorepo to say if a change affects the TRS or WES component etc. I don't think for CI it makes a lot of sense, it's not like we have a dozen different workflows or more. Also, this PR affects two CI workflows, so just having one in the scope is not quite accurate. In fact, the PR template is arguably not even directly related to CI (but okay, in this case).
Anyway, please allow PR titles not to have a scope. Or at least require it only for fix
and feat
PRs.
Make sense @uniqueg, fixed it! |
Great! 🙏 |
Description
Fixes #33
In addition to implementing the enforcement of semantic pull request titles, this update addresses the following configuration concerns within the project:
Checklist
Comments