docs(contributing): add section explaining PR review process #36044
+40
−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
- Add new section "What Happens After You Submit Your PR" to CONTRIBUTING.md - Describe CodeBuild CI validation process and steps for resolving build failures - Explain community review queue and requirements for community review - Detail maintainer review process and progression of PR through review stages - Provide guidance on monitoring PR status and addressing potential issues - Improve documentation to help contributors understand the PR submission workflow
aws-cdk-automation
previously requested changes
Nov 13, 2025
pahud
changed the title
aws-cdk-automation
dismissed
their stale review
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
- Modify text to clarify that a community review moves PR to maintainer review queue - Refine language around community review requirements - Improve precision of contribution workflow documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
We have seen many requests from the contributors asking for what's next to move forward the PR review such as
#35933 (comment)
#35819 (comment)
#35812 (comment)
#35773 (comment)
#35766 (comment)
#34202 (comment)
We need to add a section in the contributing guide about "what should we do/expect after the PR submission".
This PR essentially:
Issue # (if applicable)
Closes #.
Reason for this change
To improve the contributing experience.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license