[actions] Create issue on publish failure #2904
Closed
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
|
@passy has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
@passy has updated the pull request. You must reimport the pull request before landing. |
facebook-github-bot
added
the
CLA Signed
|
@passy has updated the pull request. You must reimport the pull request before landing. |
|
@passy has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
@passy has updated the pull request. You must reimport the pull request before landing. |
|
Rebasing so the |
|
@passy has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Pull Request Test Coverage Report for Build 1278053094
💛 - Coveralls |
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.
Summary
Because the publish runs aren't triggered on the main branch, we have limited visibility. Sending push notifications, webhooks or email integrations are hard, but opening an issue seems like a decent work-around for this.
We can broaden this to more publish actions as needed.
Test Plan
Ran on my fork which generated this issue: passy#9