kind:change

title:New scopes for managing repository hooks

created_at:2014-02-10

author_name:pengwynn

Many third party services need to set up[hooks][] in order to act upon events

in your repositories. Today, we've introduced three new[scopes][] that provide

more granular access to your repository hooks without allowing access to your

repository contents:

*`read:repo_hook` grants read access to hooks in public or private repositories.

*`write:repo_hook` grants read and write access to hooks in public or private repositories.

*`admin:repo_hook` grants read, write, and delete access to hooks in public or private repositories.

As always, if you have any questions or feedback,[get in touch][contact].

[hooks]:http://developer.github.com/v3/repos/hooks/

[scopes]:http://developer.github.com/v3/oauth/#scopes

[contact]:https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes

`delete_repo`| Grants access to delete adminable repositories.

`notifications`| Grants read access to a user's notifications.`repo` also provides this access.

`gist`| Grants write access to gists.

`read:repo_hook`| Grants read access to hooks in public or private repositories.

`write:repo_hook`| Grants read and write access to hooks in public or private repositories.

`admin:repo_hook`| Grants read, write, and delete access to hooks in public or private repositories.

NOTE: Your application can request the scopes in the initial redirection. You

can specify multiple scopes by separating them with a comma: