Bot script to automerge SDK documentation changes #4996
+196
−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
…that only target files in their repsective directories in the repository based on the team membership of the user submitting the PR. This will also automatically append a label indicating it was automerged and for which language for easy retroactive discvoery and review by docs maintainers. Signed-off-by: Whit Waldo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Added bot script to allow SDK maintainers to automerge non-draft PRs that only target files in their respective directories in the repository based on the team membership of the user submitting the PR. This will also automatically append a label indicating it was automerged and for which language for easy retroactive discovery and review by docs maintainers.
The idea is that as a .NET SDK maintainer, I should be able to make changes to .NET SDK documentation that I can merge to the target branch automatically without waiting for docs review. However, to assist the docs team in understanding which of the PRs were created and auto-merged in this way and for what language, a label will be created/attached to the PR that identifies it accordingly using a color not currently in use.
I have no idea how to test this script without putting it in here, but I generated it via Copilot, read through and corrected several obvious errors and the shape of the script appears to be accurate (I didn't validate any of the Octokit API endpoints for correctness). I'll sync with the docs maintainers in Discord to see if there's some way they want to validate this before just merging.
Issue reference