Repository navigation
chore: point every github url at the renamed majornutcracker account - #27
Merged
Merged
Conversation
Merged
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.
The GitHub account moved from
majornutcracker-devtomajornutcracker. GitHub's redirect from the old handle is not permanent, so this replaces every hardcoded reference.Changes
package.json:repository,bugs.urland theauthorprofile URLios/*.podspec:s.sourceREADME.md,docs/REFERENCE.md,docs/VERSION-UPDATE.md): example links, demo GIFs, contributing/security linksCHANGELOG.md: compare/tag link references, plus an[Unreleased]entryCONTRIBUTING.md,SECURITY.md,.github/ISSUE_TEMPLATE/config.yml,react-native-libraries-entry.json.github/CODEOWNERS:@majornutcracker-dev→@majornutcracker(GitHub does not rewrite these)The npm scope
@majornutcrackerand the native identifiers (com.majornutcracker.*) are unchanged.Why before the next release
The Release workflow publishes with
--provenance, and npm rejects the publish whenrepositorydoes not match the repo running the workflow. This has to land onmainbefore tagging 1.2.2.Checks
yarn lint,yarn test(156 passing),yarn typecheckgrep -rnI majornutcracker-devfinds nothing outsidenode_modules,buildandlocalexample/URLs return 200🤖 Generated with Claude Code