Skip running CI again when bumping connector version with /publish command
#14771
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
evantahler
changed the title
/publish command/publish command
pedroslopez
approved these changes
Jul 18, 2022
|
Very cool! |
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.
When a connector is published with the
/publishcommand, upon success, the last thing the action does is commit back changes to the manifest files (like this, for example).Since we shouldn't
/publishuntil CI is green, and the side-effects of the publish command don't modify any code in the connector's directory, running CI again seems unnecessary. Waiting until this new batch of tests is complete slows down the publishing workflow.This PR adds the magic phase
[ci skip]to the git comment the bot adds to not run CI again after a successful/publish. Learn more here.