[CI fix] Allow add-label to fail in binary-compatibility.yml - #2667
Merged
Merged
Conversation
Binary-compatibility is currently failing when attempting to add a label to the resource behind this integration when the person running the CI does not have permission to manipulate that resource. This allows that error to be ignored.
Member
|
Integrated thanks @ascopes! |
Member
|
@ascopes under which PR did you get the failure? I'm wondering if it's related to the default token permissions and if it's something we could fix. If this doesn't work with PR raised from fork branches, it kills a bit the purpose of this label. |
Contributor
Author
Member
|
Thanks, will look into it. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Binary-compatibility is currently failing when attempting to add a label to
the resource behind this integration when the person running the CI does not have
permission to manipulate that resource.
This allows that error to be ignored.