|
2 | 2 | <feed xmlns="http://www.w3.org/2005/Atom"> |
3 | 3 | <id>http://developer.github.com/</id> |
4 | 4 | <title>GitHub API Changes</title> |
5 | | - <updated>2014-07-09T00:00:00Z</updated> |
| 5 | + <updated>2014-07-28T00:00:00Z</updated> |
6 | 6 | <link rel="alternate" href="http://developer.github.com/" /> |
7 | 7 | <link rel="self" href="http://developer.github.com/changes.atom" /> |
8 | 8 | <author> |
9 | 9 | <name>technoweenie</name> |
10 | 10 | <uri>https://github.com/technoweenie</uri> |
11 | 11 | </author> |
| 12 | + <entry> |
| 13 | + <id>tag:developer.github.com,2014-07-28:/changes/2014-07-28-assignee-and-label-actions-for-issue-events/</id> |
| 14 | + <title type="html">New assigned/labeled actions for issue and pull request events</title> |
| 15 | + <published>2014-07-28T00:00:00Z</published> |
| 16 | + <updated>2014-07-28T00:00:00Z</updated> |
| 17 | + <author> |
| 18 | + <name>jdpace</name> |
| 19 | + <uri>https://github.com/technoweenie</uri> |
| 20 | + </author> |
| 21 | + <link rel="alternate" href="http://developer.github.com/changes/2014-07-28-assignee-and-label-actions-for-issue-events/" /> |
| 22 | + <content type="html"><p>As part of the <a href="https://github.com/blog/1866-the-new-github-issues">new GitHub Issues</a>, we’ve added new actions to the issues and pull requests webhook events: “labeled”, “unlabeled”, “assigned”, and “unassigned”. The payload will also include the respective assignee or label for these new actions.</p> |
| 23 | + |
| 24 | +<p>If you already have a <a href="/webhooks/">webhook</a> subscribed to the <code>issues</code> or <code>pull_request</code> events, you’ll start seeing these new actions immediately. The new events can also be fetched from the <a href="/v3/issues/events/">issue events API</a>.</p> |
| 25 | + |
| 26 | +<p>For more information, be sure to check out our documentation for the <a href="/v3/activity/events/types/#issuesevent">IssuesEvent</a> or <a href="/v3/activity/events/types/#pullrequestevent">PullRequestEvent</a>. If you have any questions or feedback, please <a href="https://github.com/contact?form%5Bsubject%5D=New+Assigned+and+Labeled+Actions+for+Issues+and+Pull+Request+Events">drop us a line</a>.</p> |
| 27 | + |
| 28 | +</content> |
| 29 | + </entry> |
12 | 30 | <entry> |
13 | 31 | <id>tag:developer.github.com,2014-07-09:/changes/2014-07-09-status-contexts-are-official/</id> |
14 | 32 | <title type="html">The Combined Status API is official</title> |
@@ -964,29 +982,6 @@ by owners of a Pages repo, whether it’s owned by an individual or an organizat |
964 | 982 | on previous Pages builds.</p> |
965 | 983 |
|
966 | 984 | <p>Enjoy!</p> |
967 | | -</content> |
968 | | - </entry> |
969 | | - <entry> |
970 | | - <id>tag:developer.github.com,2014-02-10:/changes/2014-2-10-ping-event-for-webhooks/</id> |
971 | | - <title type="html">Ping Event for Webhooks</title> |
972 | | - <published>2014-02-10T00:00:00Z</published> |
973 | | - <updated>2014-02-10T00:00:00Z</updated> |
974 | | - <author> |
975 | | - <name>kdaigle</name> |
976 | | - <uri>https://github.com/technoweenie</uri> |
977 | | - </author> |
978 | | - <link rel="alternate" href="http://developer.github.com/changes/2014-2-10-ping-event-for-webhooks/" /> |
979 | | - <content type="html"><p>With the release of our <a href="https://github.com/blog/1778-webhooks-level-up">new webhook UI</a>, we included a new |
980 | | -<a href="/webhooks/#ping-event">ping event</a> that webhooks will receive. When you |
981 | | -create a new webhook, we will send this event as an initial test of the webhook.</p> |
982 | | - |
983 | | -<p>The ping is only informational, doesn’t need to be responded to in a specific way, |
984 | | -and nothing bad will happen if you respond with an error. It’s just a quick |
985 | | -“hello world” to let you know you set everything up correctly.</p> |
986 | | - |
987 | | -<p>We also added a <a href="/v3/repos/hooks/#ping-a-hook">ping endpoint</a> to the hooks API. |
988 | | -By using ping instead of <a href="/v3/repos/hooks/#test-a-push-hook">test</a>, you can ensure |
989 | | -you won’t be limited by the <code>push</code> event requirement that the test endpoint has.</p> |
990 | 985 | </content> |
991 | 986 | </entry> |
992 | 987 | </feed> |
0 commit comments