chore(labels): add skip-changelog-orchestrator label to config #505
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
Trantorian1
added
the
infrastructure
Mohiiit
approved these changes
Mar 3, 2025
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.
Pull Request type
Please add the labels corresponding to the type of changes your PR introduces:
What is the current behavior?
The
Skip-Changeloglabel was created manually, but we have a dedicated CI process for managing labels. Since it was not initially defined in label.yml, it was not automatically synchronized with other labels.Resolves: #NA
What is the new behavior?
This PR adds the skip-changelog label definition to label.yml, ensuring that label management is handled by the CI rather than manually.
This allows the CI to consistently manage labels instead of relying on manual additions.
Does this introduce a breaking change?
No
Other information
Once this PR is good to merge, the
Sync labelsworkflow must be triggered to properly synchronize the labels across the repository, ensuring consistency between existing labels and those referenced in other workflows.