Repository navigation
chore(setup): preserve generated sources after Archive transfer - #199
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.ai>
Signed-off-by: rldyourmnd <danil@nddev.ai>
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.
Render repository registration and existing reusable CI calls from the private authoring source after the verified Archive transfer. The previous owner stays an alias; stable GDS/GitHub IDs and privacy remain unchanged.
Only the generated anchor, its native GDS projections and the CI repository address change. The two workflow files match the previous default-branch bytes after replacing the namespace; their original pinned SHA is retained (
93eeb2a65e98a29e9dbff7909f67c6419abff046). No Rust, setup, package, release or tool pin changes.Validation: the private full
scripts/gate.sh --renderpassed; generated workflow bytes satisfy the scope comparison; native projection verification passes twice after commit. No new release or tag is published.