Repository navigation
Conversation
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.
Prepare current GitHub URLs for the owner-selected username
artificenerd.Draft: merge only after Felipe confirms the GitHub account has changed from
coisatoartificenerd. This PR does not rename the account, migrate Composer package names/vendors or PHP namespaces, modify locked dependency metadata, publish packages, or change organization owners.Existing
composer-skeletonrepository suffixes are preserved; availability of that repository needs to be reconciled separately.Validation:
git diff --check HEAD^ HEADpassed.Preparation base:
cc1ad4c0f960ba82b2593675b02486dd3314dc1cPreparation head:
2820a5ae3c0733560c1e746f642e8c1d5cf8b270After the account change: confirm branch/base identity and CI, merge when authorized, then verify repository URLs, integrations and local remotes. Package/vendor/namespace migration requires a separate compatibility plan.