@@ -2582,9 +2582,9 @@ <h2 class="title">
25822582
25832583</ div >
25842584
2585- < div class ="change " id ="/changes/2014-02 -10-repo-hook-scopes / ">
2585+ < div class ="change " id ="/changes/2014-2 -10-ping-event-for-webhooks / ">
25862586 < h2 class ="title ">
2587- < a href ="/changes/2014-02 -10-repo-hook-scopes / "> New scopes for managing repository hooks </ a >
2587+ < a href ="/changes/2014-2 -10-ping-event-for-webhooks / "> Ping Event for Webhooks </ a >
25882588</ h2 >
25892589
25902590< div class ="meta ">
@@ -2595,34 +2595,29 @@ <h2 class="title">
25952595
25962596 </ li >
25972597 < li class ="who_when ">
2598- < img height ="16 " width ="16 " src ="https://github.com/pengwynn .png " alt ="Avatar for pengwynn ">
2599- < a href ="https://github.com/pengwynn " > pengwynn </ a >
2598+ < img height ="16 " width ="16 " src ="https://github.com/kdaigle .png " alt ="Avatar for kdaigle ">
2599+ < a href ="https://github.com/kdaigle " > kdaigle </ a >
26002600 </ li >
26012601</ ul >
26022602</ div >
26032603
2604- < 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
2605- in your repositories. Today, we’ve introduced three new < a href ="http://developer.github.com/v3/oauth/#scopes "> scopes</ a > that provide
2606- more granular access to your repository hooks without allowing access to your
2607- repository contents:</ p >
2608-
2609- < ul >
2610- < li >
2611- < code > read:repo_hook</ code > grants read and ping access to hooks in public or private repositories.</ li >
2612- < li >
2613- < code > write:repo_hook</ code > grants read, write, and ping access to hooks in public or private repositories.</ li >
2614- < li >
2615- < code > admin:repo_hook</ code > grants read, write, ping, and delete access to hooks in public or private repositories.</ li >
2616- </ ul >
2604+ < p > With the release of our < a href ="https://github.com/blog/1778-webhooks-level-up "> new webhook UI</ a > , we included a new
2605+ < a href ="/webhooks/#ping-event "> ping event</ a > that webhooks will receive. When you
2606+ create a new webhook, we will send this event as an initial test of the webhook.</ p >
26172607
2618- < 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 >
2608+ < p > The ping is only informational, doesn’t need to be responded to in a specific way,
2609+ and nothing bad will happen if you respond with an error. It’s just a quick
2610+ “hello world” to let you know you set everything up correctly.</ p >
26192611
2612+ < p > We also added a < a href ="/v3/repos/hooks/#ping-a-hook "> ping endpoint</ a > to the hooks API.
2613+ By using ping instead of < a href ="/v3/repos/hooks/#test-a-push-hook "> test</ a > , you can ensure
2614+ you won’t be limited by the < code > push</ code > event requirement that the test endpoint has.</ p >
26202615
26212616</ div >
26222617
2623- < div class ="change " id ="/changes/2014-2 -10-ping-event-for-webhooks / ">
2618+ < div class ="change " id ="/changes/2014-02 -10-repo-hook-scopes / ">
26242619 < h2 class ="title ">
2625- < a href ="/changes/2014-2 -10-ping-event-for-webhooks / "> Ping Event for Webhooks </ a >
2620+ < a href ="/changes/2014-02 -10-repo-hook-scopes / "> New scopes for managing repository hooks </ a >
26262621</ h2 >
26272622
26282623< div class ="meta ">
@@ -2633,23 +2628,28 @@ <h2 class="title">
26332628
26342629 </ li >
26352630 < li class ="who_when ">
2636- < img height ="16 " width ="16 " src ="https://github.com/kdaigle .png " alt ="Avatar for kdaigle ">
2637- < a href ="https://github.com/kdaigle " > kdaigle </ a >
2631+ < img height ="16 " width ="16 " src ="https://github.com/pengwynn .png " alt ="Avatar for pengwynn ">
2632+ < a href ="https://github.com/pengwynn " > pengwynn </ a >
26382633 </ li >
26392634</ ul >
26402635</ div >
26412636
2642- < p > With the release of our < a href ="https://github.com/blog/1778-webhooks-level-up "> new webhook UI</ a > , we included a new
2643- < a href ="/webhooks/#ping-event "> ping event</ a > that webhooks will receive. When you
2644- create a new webhook, we will send this event as an initial test of the webhook.</ p >
2637+ < 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
2638+ in your repositories. Today, we’ve introduced three new < a href ="http://developer.github.com/v3/oauth/#scopes "> scopes</ a > that provide
2639+ more granular access to your repository hooks without allowing access to your
2640+ repository contents:</ p >
26452641
2646- < p > The ping is only informational, doesn’t need to be responded to in a specific way,
2647- and nothing bad will happen if you respond with an error. It’s just a quick
2648- “hello world” to let you know you set everything up correctly.</ p >
2642+ < ul >
2643+ < li >
2644+ < code > read:repo_hook</ code > grants read and ping access to hooks in public or private repositories.</ li >
2645+ < li >
2646+ < code > write:repo_hook</ code > grants read, write, and ping access to hooks in public or private repositories.</ li >
2647+ < li >
2648+ < code > admin:repo_hook</ code > grants read, write, ping, and delete access to hooks in public or private repositories.</ li >
2649+ </ ul >
2650+
2651+ < 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 >
26492652
2650- < p > We also added a < a href ="/v3/repos/hooks/#ping-a-hook "> ping endpoint</ a > to the hooks API.
2651- By using ping instead of < a href ="/v3/repos/hooks/#test-a-push-hook "> test</ a > , you can ensure
2652- you won’t be limited by the < code > push</ code > event requirement that the test endpoint has.</ p >
26532653
26542654</ div >
26552655
@@ -3616,9 +3616,9 @@ <h2 class="title">
36163616
36173617</ div >
36183618
3619- < div class ="change " id ="/changes/2013-05-06-repository-stats / ">
3619+ < div class ="change " id ="/changes/2013-05-06-create-update-delete-individual-files / ">
36203620 < h2 class ="title ">
3621- < a href ="/changes/2013-05-06-repository-stats / "> Repository Statistics </ a >
3621+ < a href ="/changes/2013-05-06-create-update-delete-individual-files / "> Create, update, and delete individual files </ a >
36223622</ h2 >
36233623
36243624< div class ="meta ">
@@ -3629,33 +3629,25 @@ <h2 class="title">
36293629
36303630 </ li >
36313631 < li class ="who_when ">
3632- < img height ="16 " width ="16 " src ="https://github.com/Caged .png " alt ="Avatar for Caged ">
3633- < a href ="https://github.com/Caged " > Caged </ a >
3632+ < img height ="16 " width ="16 " src ="https://github.com/ymendel .png " alt ="Avatar for ymendel ">
3633+ < a href ="https://github.com/ymendel " > ymendel </ a >
36343634 </ li >
36353635</ ul >
36363636</ div >
36373637
3638- < p > Today we’re happy to open our < a href ="/v3/repos/statistics "> Repository Statistics API</ a > to everyone. We’re using
3639- repository statistics to power < a href ="https://github.com/github/linguist/graphs "> our graphs</ a > ,
3640- but we can’t wait to see what others can do with this information.</ p >
3641-
3642- < p > Starting today, these resources are available to you:</ p >
3638+ < p > We’re following in the footsteps of GitHub.com’s ability to < a href ="https://github.com/blog/143-inline-file-editing "> edit</ a > and
3639+ < a href ="https://github.com/blog/1327-creating-files-on-github "> create</ a > files in your web browser. Starting today, the
3640+ < a href ="/v3/repos/contents/ "> Repository Contents API</ a > will let you easily < a href ="/v3/repos/contents/#create-a-file "> create</ a > , < a href ="/v3/repos/contents/#update-a-file "> update</ a > , and even
3641+ < a href ="/v3/repos/contents/#delete-a-file "> delete</ a > individual files.</ p >
36433642
3644- < ul >
3645- < li > < strong > < a href ="/v3/repos/statistics/#contributors "> Contributors</ a > </ strong > </ li >
3646- < li > < strong > < a href ="/v3/repos/statistics/#commit-activity "> Commit Activity</ a > </ strong > </ li >
3647- < li > < strong > < a href ="/v3/repos/statistics/#code-frequency "> Code Frequency</ a > </ strong > </ li >
3648- < li > < strong > < a href ="/v3/repos/statistics/#participation "> Participation</ a > </ strong > </ li >
3649- < li > < strong > < a href ="/v3/repos/statistics/#punch-card "> Punch Card</ a > </ strong > </ li >
3650- </ ul >
3643+ < p > Happy editing!</ p >
36513644
3652- < p > Enjoy!</ p >
36533645
36543646</ div >
36553647
3656- < div class ="change " id ="/changes/2013-05-06-create-update-delete-individual-files / ">
3648+ < div class ="change " id ="/changes/2013-05-06-repository-stats / ">
36573649 < h2 class ="title ">
3658- < a href ="/changes/2013-05-06-create-update-delete-individual-files / "> Create, update, and delete individual files </ a >
3650+ < a href ="/changes/2013-05-06-repository-stats / "> Repository Statistics </ a >
36593651</ h2 >
36603652
36613653< div class ="meta ">
@@ -3666,19 +3658,27 @@ <h2 class="title">
36663658
36673659 </ li >
36683660 < li class ="who_when ">
3669- < img height ="16 " width ="16 " src ="https://github.com/ymendel .png " alt ="Avatar for ymendel ">
3670- < a href ="https://github.com/ymendel " > ymendel </ a >
3661+ < img height ="16 " width ="16 " src ="https://github.com/Caged .png " alt ="Avatar for Caged ">
3662+ < a href ="https://github.com/Caged " > Caged </ a >
36713663 </ li >
36723664</ ul >
36733665</ div >
36743666
3675- < p > We’re following in the footsteps of GitHub.com’s ability to < a href ="https://github.com/blog/143-inline-file-editing "> edit</ a > and
3676- < a href ="https://github.com/blog/1327-creating-files-on-github "> create</ a > files in your web browser. Starting today, the
3677- < a href ="/v3/repos/contents/ "> Repository Contents API</ a > will let you easily < a href ="/v3/repos/contents/#create-a-file "> create</ a > , < a href ="/v3/repos/contents/#update-a-file "> update</ a > , and even
3678- < a href ="/v3/repos/contents/#delete-a-file "> delete</ a > individual files.</ p >
3667+ < p > Today we’re happy to open our < a href ="/v3/repos/statistics "> Repository Statistics API</ a > to everyone. We’re using
3668+ repository statistics to power < a href ="https://github.com/github/linguist/graphs "> our graphs</ a > ,
3669+ but we can’t wait to see what others can do with this information.</ p >
36793670
3680- < p > Happy editing!</ p >
3671+ < p > Starting today, these resources are available to you:</ p >
3672+
3673+ < ul >
3674+ < li > < strong > < a href ="/v3/repos/statistics/#contributors "> Contributors</ a > </ strong > </ li >
3675+ < li > < strong > < a href ="/v3/repos/statistics/#commit-activity "> Commit Activity</ a > </ strong > </ li >
3676+ < li > < strong > < a href ="/v3/repos/statistics/#code-frequency "> Code Frequency</ a > </ strong > </ li >
3677+ < li > < strong > < a href ="/v3/repos/statistics/#participation "> Participation</ a > </ strong > </ li >
3678+ < li > < strong > < a href ="/v3/repos/statistics/#punch-card "> Punch Card</ a > </ strong > </ li >
3679+ </ ul >
36813680
3681+ < p > Enjoy!</ p >
36823682
36833683</ div >
36843684
0 commit comments