fix(ci): remove stale GemReward gitlink - #49
Draft
zedarvates wants to merge 2 commits into
Draft
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.



Summary
Repairs the repository-level checkout defect tracked in #48 without restoring or disclosing any submodule URL.
GemReward-Service-Repogitlink;GemReward-Service-Staging/tree unchanged;actions/checkout@v4proof workflow withcontents: readonly.Canonical-state evidence
cdb9231on 2026-03-08 without a matching.gitmodulesentry;.gitmodulesentry for this path;GemReward-Service-Repo;GemReward-Service-Staging/;41d4225only advanced the opaque gitlink commit and did not establish valid submodule metadata.This makes deletion—not URL reconstruction—the smallest non-secret-bearing repair.
Validation
The PR's
Repository Checkout CIjob intentionally contains onlyactions/checkout@v4. A green run proves the repository can be checked out through the normal action without the semantic-prevalidator tarball workaround.No private repository URL is added or exposed. No project code is changed.
Closes #48.