> For the complete documentation index, see [llms.txt](https://docs.onlydust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlydust.com/contributors-hiya/why-github-authorizations.md). # Why GitHub authorizations ### In a few words We need the authorizations in order to allow you to have the BEST EXPERIENCE ever on OnlyDust. Or else it’s really limited and actually, not worth it 😟. Contributors log in via the **OnlyDust OAuth App**. This is required only when applying to an issue. Here's how permissions work: #### Permissions requested **`read:user`** Used to: * Fetch contributor profile and public GitHub activity * Feed our recommendation engine and contributor scoring * Display profile data in the app We call the GitHub API using the contributor’s token. This avoids rate-limiting issues (5000 req/h per token) that we’d hit using a single platform token. No GitHub connection = no real login. Contributor gets read-only access. * First time: contributor is asked to grant this permission during the application modal * Later applications: no prompt unless the permission was revoked * If permission is revoked: we’ll ask again This permission lets us comment on GitHub issues **as the contributor**. [GitHub OAuth scopes reference](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps) over here. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.onlydust.com/contributors-hiya/why-github-authorizations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.