Implemented in #3 (branch named-remotes on top of this PR). Switches GitClone to a remotes=[{"name": ..., "url": ...}, ...] API so each remote gets the name you pick (github / gitea_admin / gitea_hermes in the configs). The positional-list shorthand from this PR is kept for back-compat, so test_git_clone_multiple_urls keeps working. PR #3 also adds test_git_clone_named_remotes and a validation test covering every rejection path.
Implemented in #3 (branch `named-remotes` on top of this PR). Switches `GitClone` to a `remotes=[{"name": ..., "url": ...}, ...]` API so each remote gets the name you pick (`github` / `gitea_admin` / `gitea_hermes` in the configs). The positional-list shorthand from this PR is kept for back-compat, so `test_git_clone_multiple_urls` keeps working. PR #3 also adds `test_git_clone_named_remotes` and a validation test covering every rejection path.
admin
marked the pull request as work in progress 2026-08-23 20:10:07 +02:00
admin
marked the pull request as ready for review 2026-08-23 20:10:32 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I would like to give names for remotes
Implemented in #3 (branch
named-remoteson top of this PR). SwitchesGitCloneto aremotes=[{"name": ..., "url": ...}, ...]API so each remote gets the name you pick (github/gitea_admin/gitea_hermesin the configs). The positional-list shorthand from this PR is kept for back-compat, sotest_git_clone_multiple_urlskeeps working. PR #3 also addstest_git_clone_named_remotesand a validation test covering every rejection path.Pull request closed