You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a repo is cloned using ssh, it has the .git suffix in its remote url in .git/config.
This is correctly detected from todocheck as a github configuration. However, all subsequent calls for issues fail as the github API doesn't consider github.com/user/repo.git the same as github.com/user/repo.
See example:
In the image above, I have a private repo setup, called todocheck-mock with issues 1 (closed) and 2 (open). todocheck incorrectly detects both issues as non-existent as the API calls are not targeted towards the right repo.
The text was updated successfully, but these errors were encountered:
When a repo is cloned using ssh, it has the
.git
suffix in its remote url in.git/config
.This is correctly detected from todocheck as a github configuration. However, all subsequent calls for issues fail as the github API doesn't consider
github.com/user/repo.git
the same asgithub.com/user/repo
.See example:
In the image above, I have a private repo setup, called
todocheck-mock
with issues 1 (closed) and 2 (open).todocheck
incorrectly detects both issues as non-existent as the API calls are not targeted towards the right repo.The text was updated successfully, but these errors were encountered: