chore: Remove xb command aliases to avoid conflicts with other ddev add-ons - #73
Merged
Merged
Conversation
Drop alias metadata from xb commands so they do not collide with other add-ons or project commands. Update command examples to consistently use explicit xb-* command names. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
penyaskito
force-pushed
the
chore/remove-command-aliases
branch
from
August 31, 2026 07:48
62ba2a3 to
e78fa7e
Compare
penyaskito
changed the title
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.
Drop alias metadata from xb commands so they do not collide with other add-ons or project commands. Update command examples to consistently use explicit xb-* command names.
This is needed to be able to use the xb-dev tools with other ddev extensions when working with a suite of modules to make them Canvas compatible, eg. being able to resolve Canvas issues in context of Drupal CMS with manual testing possibility.
Done with LLM assistance but is super simple :)