Use code-owner-self-merge fork that supports optional pinging
#3521
Conversation
This file contains 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
github-actions
bot
added
ci
|
Nice. This is so great |
hyperupcall
changed the title
code-owner-self-merge that supports optional pingingcode-owner-self-merge fork that supports optional pinging
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.
The upstream
OSS-Docs-Tools/code-owner-self-mergeis useful, but I thought it was missing a feature in which it would not ping certain CODEOWNERS. This is useful when a CODEOWNER watches the repositories (for pull requests) and would recieve a notification anyways, on a PR. This is helpful when prioritizing PRs in the notification page: it will show as a notification of type "review quested" instead of "mentioned".When
ownerNoPingsis configured, it looks like this: