Repository navigation
Fix Branch naming for bs_* tags and avoid matching sub-string updates - #9
Merged
Merged
Conversation
thepetk
force-pushed
the
fix-branch-naming
branch
from
February 11, 2026 11:16
3fcc7c4 to
017add3
Compare
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.
What does this PR do?
Creates a more detailed branch name for each PR just to avoid getting the
branch already existserror for legit updates scoping the same backstage version.It also makes sure that we don't update two plugins having sub-string that are matching. An example was lightspeed & lightspeed-backend.
Which issue(s) does this PR fix
N/A
How to test changes / Special notes to the reviewer
Unit tests have been added