@@ -1147,9 +1147,9 @@ <h2 class="title">
11471147
11481148</ div >
11491149
1150- < div class ="change " id ="/changes/2014-02 -10-repo-hook-scopes / ">
1150+ < div class ="change " id ="/changes/2014-2 -10-ping-event-for-webhooks / ">
11511151 < h2 class ="title ">
1152- < a href ="/changes/2014-02 -10-repo-hook-scopes / "> New scopes for managing repository hooks </ a >
1152+ < a href ="/changes/2014-2 -10-ping-event-for-webhooks / "> Ping Event for Webhooks </ a >
11531153</ h2 >
11541154
11551155< div class ="meta ">
@@ -1160,34 +1160,29 @@ <h2 class="title">
11601160
11611161 </ li >
11621162 < li class ="who_when ">
1163- < img height ="16 " width ="16 " src ="https://github.com/pengwynn .png " alt ="Avatar for pengwynn ">
1164- < a href ="https://github.com/pengwynn " > pengwynn </ a >
1163+ < img height ="16 " width ="16 " src ="https://github.com/kdaigle .png " alt ="Avatar for kdaigle ">
1164+ < a href ="https://github.com/kdaigle " > kdaigle </ a >
11651165 </ li >
11661166</ ul >
11671167</ div >
11681168
1169- < p > Many third party services need to set up < a href ="http://developer.github.com/v3/repos/hooks/ "> hooks</ a > in order to act upon events
1170- in your repositories. Today, we’ve introduced three new < a href ="http://developer.github.com/v3/oauth/#scopes "> scopes</ a > that provide
1171- more granular access to your repository hooks without allowing access to your
1172- repository contents:</ p >
1173-
1174- < ul >
1175- < li >
1176- < code > read:repo_hook</ code > grants read and ping access to hooks in public or private repositories.</ li >
1177- < li >
1178- < code > write:repo_hook</ code > grants read, write, and ping access to hooks in public or private repositories.</ li >
1179- < li >
1180- < code > admin:repo_hook</ code > grants read, write, ping, and delete access to hooks in public or private repositories.</ li >
1181- </ ul >
1169+ < p > With the release of our < a href ="https://github.com/blog/1778-webhooks-level-up "> new webhook UI</ a > , we included a new
1170+ < a href ="/webhooks/#ping-event "> ping event</ a > that webhooks will receive. When you
1171+ create a new webhook, we will send this event as an initial test of the webhook.</ p >
11821172
1183- < p > As always, if you have any questions or feedback, < a href ="https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes "> get in touch</ a > .</ p >
1173+ < p > The ping is only informational, doesn’t need to be responded to in a specific way,
1174+ and nothing bad will happen if you respond with an error. It’s just a quick
1175+ “hello world” to let you know you set everything up correctly.</ p >
11841176
1177+ < p > We also added a < a href ="/v3/repos/hooks/#ping-a-hook "> ping endpoint</ a > to the hooks API.
1178+ By using ping instead of < a href ="/v3/repos/hooks/#test-a-push-hook "> test</ a > , you can ensure
1179+ you won’t be limited by the < code > push</ code > event requirement that the test endpoint has.</ p >
11851180
11861181</ div >
11871182
1188- < div class ="change " id ="/changes/2014-2 -10-ping-event-for-webhooks / ">
1183+ < div class ="change " id ="/changes/2014-02 -10-repo-hook-scopes / ">
11891184 < h2 class ="title ">
1190- < a href ="/changes/2014-2 -10-ping-event-for-webhooks / "> Ping Event for Webhooks </ a >
1185+ < a href ="/changes/2014-02 -10-repo-hook-scopes / "> New scopes for managing repository hooks </ a >
11911186</ h2 >
11921187
11931188< div class ="meta ">
@@ -1198,23 +1193,28 @@ <h2 class="title">
11981193
11991194 </ li >
12001195 < li class ="who_when ">
1201- < img height ="16 " width ="16 " src ="https://github.com/kdaigle .png " alt ="Avatar for kdaigle ">
1202- < a href ="https://github.com/kdaigle " > kdaigle </ a >
1196+ < img height ="16 " width ="16 " src ="https://github.com/pengwynn .png " alt ="Avatar for pengwynn ">
1197+ < a href ="https://github.com/pengwynn " > pengwynn </ a >
12031198 </ li >
12041199</ ul >
12051200</ div >
12061201
1207- < p > With the release of our < a href ="https://github.com/blog/1778-webhooks-level-up "> new webhook UI</ a > , we included a new
1208- < a href ="/webhooks/#ping-event "> ping event</ a > that webhooks will receive. When you
1209- create a new webhook, we will send this event as an initial test of the webhook.</ p >
1202+ < p > Many third party services need to set up < a href ="http://developer.github.com/v3/repos/hooks/ "> hooks</ a > in order to act upon events
1203+ in your repositories. Today, we’ve introduced three new < a href ="http://developer.github.com/v3/oauth/#scopes "> scopes</ a > that provide
1204+ more granular access to your repository hooks without allowing access to your
1205+ repository contents:</ p >
12101206
1211- < p > The ping is only informational, doesn’t need to be responded to in a specific way,
1212- and nothing bad will happen if you respond with an error. It’s just a quick
1213- “hello world” to let you know you set everything up correctly.</ p >
1207+ < ul >
1208+ < li >
1209+ < code > read:repo_hook</ code > grants read and ping access to hooks in public or private repositories.</ li >
1210+ < li >
1211+ < code > write:repo_hook</ code > grants read, write, and ping access to hooks in public or private repositories.</ li >
1212+ < li >
1213+ < code > admin:repo_hook</ code > grants read, write, ping, and delete access to hooks in public or private repositories.</ li >
1214+ </ ul >
1215+
1216+ < p > As always, if you have any questions or feedback, < a href ="https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes "> get in touch</ a > .</ p >
12141217
1215- < p > We also added a < a href ="/v3/repos/hooks/#ping-a-hook "> ping endpoint</ a > to the hooks API.
1216- By using ping instead of < a href ="/v3/repos/hooks/#test-a-push-hook "> test</ a > , you can ensure
1217- you won’t be limited by the < code > push</ code > event requirement that the test endpoint has.</ p >
12181218
12191219</ div >
12201220
0 commit comments