Repository navigation
Checking specifically if there are semver labels or not. - #1475
Merged
Merged
Conversation
Contributor
|
Nice ! |
dmikusa
approved these changes
Nov 17, 2026
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
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
When dependeabot opens a PR for updating the dependencies, it adds some labels. The next workflow that is getting triggered is the label-pr.yml, where in that case, it will not add the semver label, as the existing label-pr.yml workflow, sees that there are already some labels. This PR, alters the check to be specifically whether there are semver labels or not, otherwise, the semver label can not be set, the PRs from dependabot are not getting merged automatically.
Use Cases
Checklist