Read-Only OAuth Scope on GitHub, Please?
We love @GitHub. Our processes all revolve around GitHub. Naturally by extension, we love the GitHub API, because it allows us to do creative things with GitHub. So far, we have built a few apps that rely heavily on GitHub's API: - [deppbot](https://www.deppbot.com) - A service that does automated dependency updates for Ruby apps, issued as Pull Requests - [Dasherize](http://dasherize.com) - A simple dashboard for CI and GitHub stats - [GitHub Gem Stats](http://gigest.herokuapp.com/) - A toy app for "Which RubyGems does X use?" and "Which GitHub repo uses Y gem?" Let's talk about permissions next. For both deppbot and Dasherize, we require access to both public and private repos. Looking at [GitHub's OAuth scopes](https://developer.github.com/v3/oauth/#scopes), we'll need to use the `repo` scope.  Hmm.. But wait a minute.. The `repo` scope grants `read` AND `write` access to basically everything! Getting `read` access is probably a must for all apps, but do we need `write` on everything? Due to the nature of deppbot, we'll need `write` permission on public and private repos, so that it can issue Pull Requests when it finishes the dependency update for a project and perform other actions. However, all Dasherize does is `read` from public or private repos, and it's not doing any `write` at all. You can even take a look at
Posted by winston on Oct 18, 2015, 7:19 AM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
Read-Only OAuth Scope on GitHub, Please?
We love @GitHub. Our processes all revolve around GitHub. Naturally by extension, we love the GitHub API, because it allows us to do creative things with GitHub. So far, we have built a few apps that rely heavily on GitHub's API: - [deppbot](https://www.deppbot.com) - A service that does automated dependency updates for Ruby apps, issued as Pull Requests - [Dasherize](http://dasherize.com) - A simple dashboard for CI and GitHub stats - [GitHub Gem Stats](http://gigest.herokuapp.com/) - A toy app for "Which RubyGems does X use?" and "Which GitHub repo uses Y gem?" Let's talk about permissions next. For both deppbot and Dasherize, we require access to both public and private repos. Looking at [GitHub's OAuth scopes](https://developer.github.com/v3/oauth/#scopes), we'll need to use the `repo` scope.  Hmm.. But wait a minute.. The `repo` scope grants `read` AND `write` access to basically everything! Getting `read` access is probably a must for all apps, but do we need `write` on everything? Due to the nature of deppbot, we'll need `write` permission on public and private repos, so that it can issue Pull Requests when it finishes the dependency update for a project and perform other actions. However, all Dasherize does is `read` from public or private repos, and it's not doing any `write` at all. You can even take a look at
Comments (0)
No comments yet. Start the discussion.