-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use same GitHub token logic as gh #153
Comments
after getting a 401 for I think an expired GITHUB_GRAPHQL_TOKEN I had in my .Renviron I ran |
Yes indeed, that should be done. The reason not is that i don't use the git credentials store, because i have my own wacky encrypted authorization system so i can push to multiple remotes with one command. But my idiosyncracies shouldn't make it more difficult for other people to use this package. I'll update my own workflow, and then get to this straight after that. Thanks! |
In that case you'd just need to replace the current function with Now I am curious about your complex workflow, sounds like a good tech note topic. 😁 |
No, it's not, and not recommended for anybody else. It was just a fun coding exercise. Also because i like having a pasword prompt after |
or even the gh function?
Asking this as I am getting a 401.
The text was updated successfully, but these errors were encountered: