Repository navigation
chore: align project metadata with RexCode - #61
Closed
efegokdemir wants to merge 1 commit into
Closed
efegokdemir wants to merge 1 commit into
efegokdemir wants to merge 1 commit into
Conversation
Member
Author
|
Superseded by #64, a clean PR based on current main containing only the useful remaining metadata changes. #62 is already merged and its canonical URL/contribution changes are present. The maintainers team visibility and explicit repository write access were verified; the replacement preserves current contribution terms and the existing release-alias job. #61 is not being 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
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.
Canonical repository and support links now point to RexCode-Digital; maintenance metadata and Action examples are aligned with the organization. The release workflow no longer force-moves minor alias tags; existing tags remain intact. No licensing, history, or source ownership claim was changed. Validation: 101 tests, lint, coverage, package smoke check, action bundle check, npm audit (0 vulnerabilities), and git diff --check passed.