fix: add branch alias for main (backport: 6.6.x)#14951
Merged
Soner (shyim) merged 1 commit into6.6.xfrom Feb 13, 2026
Merged
Conversation
shopware-octo-sts-app-2
bot
requested a review
from Jonas Elfering (keulinho)
shopware-octo-sts-app-2
bot
added
component/core
domain/framework
github-actions
bot
added
the
external-contribution
|
Soner (shyim)
force-pushed
the
fix/add-main-branch-alias-backport-6.6.x
branch
from
62aae35 to
ffa34c1
Compare
Soner (shyim)
approved these changes
Feb 13, 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
1 participant
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.
Backport: #14820
1. Why is this change necessary?
I added a alias local for trunk to main, so I don't have to remember to merge / rebase against trunk. This seems to fuck up composer dependency resolving
2. What does this change do, exactly?
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist
RELEASE_INFO-6.<major>.mdunder “Upcoming” for informational changes, including the consequences of the change and how it affects external developers.UPGRADEsection inUPGRADE-6.<next-major>.mdfor breaking changes (what/why/impact/how to adapt).