Skip to content
This repository has been archived by the owner on Nov 1, 2017. It is now read-only.

Commit

Permalink
Add note on repo:status scope
Browse files Browse the repository at this point in the history
  • Loading branch information
rsanheim committed Aug 30, 2012
1 parent 5d431b1 commit 77c7f3c
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 0 deletions.
1 change: 1 addition & 0 deletions content/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ The API is expected to be finalized Real Soon Now.
### Breaking Beta Changes

##### August 30, 2012
* Added `repo:status` scope
* Added Status API

##### August 7, 2012
Expand Down
4 changes: 4 additions & 0 deletions content/v3/oauth.md
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,10 @@ public\_repo
repo
: Read/write access to public and private repos and organizations.

repo:status
: Read/write access to public and private repo statuses. Does **not**
include access to code - use `repo` for that.

delete\_repo
: Delete access to adminable repositories.

Expand Down

2 comments on commit 77c7f3c

@jasonm
Copy link

@jasonm jasonm commented on 77c7f3c Jan 19, 2013

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rsanheim I'm wondering if this could use clarification. The way I originally read the docs, I was confused and thought that repo:status was necessary even for updating Commit Status on public repos. It's not, and public_repo scope suffices for this. I had discussion https://github.com/jasonm/clahub/issues/17 about this and wonder if the fact that public_repo also includes the rights of a hypothetical public_repo:status could be clarified here.

Or if I just need to learn to read good 😄

@pengwynn
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, clarified in 5d8da79

Please sign in to comment.