Skip to content

CI: authenticate Forgejo git dependencies after transfer - #2

Closed
thedancingdeveloper wants to merge 8 commits into
mainfrom
ci/forgejo-auth-after-transfer-20260722
Closed

CI: authenticate Forgejo git dependencies after transfer#2
thedancingdeveloper wants to merge 8 commits into
mainfrom
ci/forgejo-auth-after-transfer-20260722

Conversation

@thedancingdeveloper

Copy link
Copy Markdown
Collaborator

Reapply the recorded post-transfer CI credential rewrite for internal Forgejo git dependencies.

@thedancingdeveloper

Copy link
Copy Markdown
Collaborator Author

Heads-up from the CI-backlog pass: this PR's premise — authenticate CI to the Forgejo git dependencies — is superseded by the decision to migrate off Forgejo to GitHub instead (see #4). The sibling crates (librtbit-upnp-serve, librtbit-lsd) are already migrated and building on GitHub sources.

This PR also carries unrelated source changes (src/http_api_client.rs, src/storage/filesystem/fs.rs, src/torrent_state/live/peer_handler.rs), so it shouldn't just be closed. Suggest rebasing to drop the ci.yml Forgejo-credential change and keeping/reviewing the source edits on their own — or closing if they're stale.

@thedancingdeveloper

Copy link
Copy Markdown
Collaborator Author

Closing as fully superseded:

Nothing left to salvage.

@thedancingdeveloper
thedancingdeveloper deleted the ci/forgejo-auth-after-transfer-20260722 branch August 24, 2026 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant