GitOS 0.1.3

Work with organization repositories, without waiting for approval

New: sign in with an access token

Organizations can block apps they haven't approved, and GitHub turns this on by default for new organizations. When that happens, their private repositories look like they don't exist to GitOS, even if your account has access and other apps work fine.

You can now add an account with a classic personal access token instead:

1. Go to Settings › Accounts › + and click Use a Token…
2. Click Create a Classic Token on GitHub. The permissions GitOS needs are already ticked.
3. Paste the token and click Add Account.

If you've already added that account, the token replaces its existing sign-in. Your token is stored in your Keychain.

Good to know:

• Tokens don't need organization approval, unless the organization blocks classic tokens. If it does, an owner needs to approve GitOS.
• If the organization uses SSO, also click Configure SSO next to the token on GitHub.
• A classic token can reach everything your account can, so set an expiry date. When it expires, add a new one with Use a Token…
• Check your organization's rules before using a token on work code.

Fixed

• Misleading "Repository not found" advice. GitOS used to suggest you had the wrong account. For repositories you don't own, it now explains that the organization may need to approve GitOS.
• Faster way out of that error. The error now offers Use an Access Token… and Review Access on GitHub, so you can fix it from there.

Full Changelog: v0.1.2...v0.1.3