build: Drop the comment workflow #219
Merged
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 workflow introduced in citynetwork#218, intended to facilitate pull requests by adding a comment in case the PR produced any build errors, failed on its first test. A build failure on citynetwork#217 did cause the action to fire, but it immediately failed with the following message: Run quipper/[email protected] No open pull requests found with packettoobig-patch-1 branch Since a pull request from that branch obviously did exist, it follows that the action isn't working as intended, so drop it and rely on per-user build notifications, set via https://github.com/settings/notifications, instead.
|
@colder-is-better Apologies for the noise. 'Twas worth a shot. :) |
colder-is-better
approved these changes
Aug 16, 2023
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 workflow introduced in #218, intended to facilitate pull requests by adding a comment in case the PR produced any build errors, failed on its first test. A build failure on #217 did cause the action to fire, but it immediately failed with the following message:
Since a pull request from that branch obviously did exist, it follows that the action isn't working as intended, so drop it and rely on per-user build notifications, set via https://github.com/settings/notifications, instead.