This is one of at least a couple of possible ways to fix #12.
Worth noting: @guites had previously suggested an alternative approach at https://github.com/diracdeltas/tweets/issues/12#issuecomment-1305460820 which would involve a single HTTP request per remote -- basically to validate whether the forks listed by GitHub are accessible to the user before the fetch occurs.
It's kinda awkward to use an environment variable for this setting, but we can't (as far as I know, and probably sensibly by-design) make git infer it from any of the contents of the repository itself. On the plus side, this should use fewer overall HTTP requests (n vs 2n).
diracdeltas
commented
2 years ago
This is one of at least a couple of possible ways to fix #12.
Worth noting: @guites had previously suggested an alternative approach at https://github.com/diracdeltas/tweets/issues/12#issuecomment-1305460820 which would involve a single HTTP request per remote -- basically to validate whether the forks listed by GitHub are accessible to the user before the fetch occurs.
It's kinda awkward to use an environment variable for this setting, but we can't (as far as I know, and probably sensibly by-design) make
gitinfer it from any of the contents of the repository itself. On the plus side, this should use fewer overall HTTP requests (nvs2n).Resolves #12.