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
i'm addig this as a potential bug. I know that token="" When working with github.remote_repo exists. If you don't have a token or the token is BAD, it returns false even if the repo does exist.
i need to work on the test a bit more but right now if the token is bad it will return a false. what i don't know is if the bad token will always be caught before that check so i'm opening this knowing it may be addressed elsewhere but i don't see that yet. it is called once in template.py when we update the template repo.
The text was updated successfully, but these errors were encountered:
lwasser
changed the title
potential bug? - github.remote_repo_exists
potential bug? - github.remote_repo_exists returns false with bad token even if repo exists.
Nov 16, 2021
i'm addig this as a potential bug. I know that token="" When working with github.remote_repo exists. If you don't have a token or the token is BAD, it returns false even if the repo does exist.
Try this:
github.remote_repo_exists("earthlab", "earthpy", token="sdf")
i need to work on the test a bit more but right now if the token is bad it will return a
false
. what i don't know is if the bad token will always be caught before that check so i'm opening this knowing it may be addressed elsewhere but i don't see that yet. it is called once in template.py when we update the template repo.The text was updated successfully, but these errors were encountered: