Github actions workflow to notify extension managers when there are errors or warnings #1984
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
the point of contacts was generated by github api by checking contributors and people who merged the most recent pull request
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.
This workflow does not interfere if an extension already has a point of contact. However, it will automatically check for new extensions that do not have a CODEOWNER. Whether you choose to commit the updated CODEOWNERS back to the repo when an extension lacks a CODEOWNER is entirely up to you. I can add another step to the workflow to accommodate this.
If there is a GitHub issue created for an extension already, I do not update it. Should we? I do not know if some extensions are maintained anymore, so we will have a long thread if errors or warnings are not addressed promptly. Do you think, updating an issue with up to 5 consecutive days of builds (with errors or warnings) using comments will be a good idea?
Please note that a limitation of this workflow is that non-GitHub repositories cannot be notified.
Take a look at issues created and closed by GitHub actions bot in my fork. https://github.com/vkt1414/ExtensionsIndex/issues
Looking forward to your feedback.
Thanks to @jcfr @fedorov @pieper for guidance.