ci: enforce PR template and related reference checks#4228
Open
Yicong-Huang wants to merge 2 commits intomainfrom
Open
ci: enforce PR template and related reference checks#4228Yicong-Huang wants to merge 2 commits intomainfrom
Yicong-Huang wants to merge 2 commits intomainfrom
Conversation
Contributor
|
-1 on this. Having PR and issue templates is a nice-to-have. They provide guidance while still giving contributors flexibility. If we want to strictly enforce the template, we would need to go through the Apache voting process. It was acceptable to hold only a poll on the template when it was merely a suggestion. However, if we intend to enforce it, a formal vote would be required. |
Contributor
|
@Yicong-Huang If you agree, we can do a discussion on the dev email list and do a vote. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
This PR adds/updates PR lint checks to enforce PR template usage and related issue/discussion references, with a minor-title fallback.
Any related issues, documentation, discussions?
Closes #4227
How was this PR tested?
Verified workflow syntax and script logic locally by inspecting the updated workflow file and diff.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)