Added a new guideline describing overall PR Review process #931
+102
−0
Conversation
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
|
Hi @benjagm , kindly review this PR at your convenience and suggest some feedbacks/changes if applicable. |
benjagm
previously approved these changes
Jul 17, 2025
benjagm
requested changes
Jul 17, 2025
|
Hi @benjagm , I have moved the file to /programs/triage-group as instructed by you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GitHub Issue: #926
Summary:
Through this PR, I have added a detailed PR review process guideline. To ensure consistency, clarity, and efficiency across all contributions, we need to define a comprehensive guideline for the Pull Request (PR) review process. This document should serve as a go-to reference for both contributors and maintainers, outlining the expectations, standards, and steps involved during PR reviews.
Do you think resolving this issue might require an Architectural Decision Record (ADR)? (significant or noteworthy)
No