Mislav Marohnić

Yes, as you've discovered, the token is stored in plain text. We plan to improve that; follow https://github.com/cli/cli/issues/449 for updates. Git Credential Manager is indeed great for managing credentials for...

No, we don't do anything with rate limit information at the moment. How would you expect rate limit information to be handled in CLI?

Thanks for explaining! It's definitely within our possibilities to include support for throttling. However, the guides that you linked are meant for more general API clients, a lot of which...

I'm wondering whether gh should exit with a special error code when it encounters a rate limit error? https://github.com/cli/cli/blob/2ab073d599b1a64bd58af0ddc6eed63d3a0deb65/cmd/gh/main.go#L36-L43 With that, people writing automation may choose to handle that exit...

Copying over feedback from a related issue where @sambostock writes: > ### Expected vs actual behavior > `gh api --paginate ...` **should**: > > * avoid encountering rate limits, **or**...

@jsoref Writing ratelimit information to a file of your choosing is not a bad idea! But if you use `gh api` for making requests, you can opt to see response...

Update: we've discussed this as length and considered several approaches. We decided against writing rate limit information to a separate file, and in favor of optionally providing rate limit information...

There were feature requests floating around for a while proposing across-the-board support for overriding the repo (or specifying [another git remote](https://github.com/github/hub/issues/1973)) for any hub command, which would then include `hub...

@lersek I cannot follow what you've describe really well, but you're right that you can't open a Pull Request on GitHub from a repo that isn't a github-fork (or, at...

@gvela024 Go right ahead! 🙏