Already applied labels not skipping node updates #15
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
…gets to match This isn’t a microservice, dummy – it’s an operator which has releases. 🤦
This includes a regression test to prevent this from happening in the future.
The `tools` profile doesn’t build it and the `dev` profile uses a different build command anyways.
…e a manual trigger
annismckenzie
force-pushed
the
already-applied-labels-not-skipping-node-updates
branch
from
86e1b1f
to
227896c
Compare
|
Lookin' great – merging. |
annismckenzie
deleted the
already-applied-labels-not-skipping-node-updates
branch
annismckenzie
added
bug
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 fixes #14. I'm releasing v0.1.2.