We are experimenting with changes to the "Hookshot" backend that powers service hooks. There were some significant networking changes with the new cluster, so there are some new IP whitelist rules for hooks:
These are in CIDR notation. They represent a significant range of GitHub addresses, meaning this should be the last IP change for a while. Once this cluster is activated and we shut the other cluster down, we will be removing the other entries.
We are currently testing the new backend with all repositories in the GitHub organization only, and expect to start testing it with user data next week.
This also means we should be able to start accepting GitHub Services pull requests very soon :)
We had an issue with the Hookshot load balancer this morning, causing the majority of hooks to flow to a single node only. This lead to massive queue times. While fixing this, we're putting the old Services backend in use.
This means the old IPs are back in use. Use this Help guide if you already removed them from your firewall.
We turned Hookshot (our new GitHub Services backend) on yesterday. Things have been pretty smooth, with one issue: Hooks going to other EC2 nodes come from the private IP addresses of our nodes in the 10...* range.
If your web hook servers are on EC2 and are missing hooks from GitHub due to an IP restriction, we recommend the following:
- Remove the IP white list.
- Fall back to HTTPS and Basic Auth to restrict pushes to authorized senders only.
We're currently working on solving this problem.
We are finishing up a new GitHub Services backend, dubbed "Hookshot", to increase the speed and reliability of our delivered payloads. We are doing what we can to make this a seamless transition for everyone. However, there are a few notable changes.
There is a new Meta API endpoint listing the current public IPs that hooks originate from.
We're removing the AMQP service from GitHub. It hasn't worked in quite some time, and the code it uses doesn't work in our background workers.
We're also instituting a new guideline to improve the reliability and maintainability of services in the future. As of today, all new services must accept an unmodified payload over HTTP. Any service that does not will be rejected. To see an example of an acceptable service, check out Code Climate. Notice their service simply accepts HTTP POST from GitHub unmodified. For an example of a service that won't be accepted after today, check out Campfire. It uses other Ruby gems and contains custom logic to transform the GitHub payload to Campfire messages. Existing hooks will keep working (don't worry 37signals, we Campfire).
We're making these changes because we want to focus on the reliability of the core Services backend for everyone. Maintaining custom logic and libraries for over 100 services is taking too much of this focus away.
Following on from our previous post about requiring requests to include a valid User Agent header we will soon be changing our API servers to return HTTP 403 to any clients not providing a valid User Agent header.
We will be making this change on Monday, March 4th 2013.
Setting this helps us identify requests from you, and get in touch with people who are using the API in a way which causes disruption to GitHub. Most HTTP libraries and tools like cURL already provide a valid header for you, and allow you to customize it, so this will not require many of our users to make any changes whatsoever.
If you have any questions or feedback, please drop us a line.
We've added a few new user scopes for 3rd party applications that want very
specific user functionality. The
user:email scope gives apps read-only access
to a user's private email addresses. The
user:follow scope lets a user
follow and unfollow other users.
This should help keep applications from requiring the
user scope, which
can be potentially dangerous.
We also added a read-only endpoint to get a user's public SSH keys.
Starting today, you can get
.patch content directly from the API for the following resources:
Simply use the same resource URL and send either
application/vnd.github.patch in the
curl -H "Accept: application/vnd.github.diff" $ https://api.github.com/repos/pengwynn/dotfiles/commits/aee60a4cd56fb4c6a50e60f17096fc40c0d4d72c diff --git a/tmux/tmux.conf.symlink b/tmux/tmux.conf.symlink index 1f599cb..abaf625 100755 --- a/tmux/tmux.conf.symlink +++ b/tmux/tmux.conf.symlink @@ -111,6 +111,7 @@ set-option -g base-index 1 ## enable mouse set-option -g mouse-select-pane on set-option -g mouse-select-window on +set-option -g mouse-resize-pane on set-window-option -g mode-keys vi set-window-option -g mode-mouse on # set-window-option -g monitor-activity off
Improvements continue to the Organizations Repository listing endpoint.
Today we're improving pagination so that it works as documented. Now
you can expect
Link headers to navigate through the results space,
regardless of what you send in the
The docs for Organization Repositories queries are still here:
Link headers are our preferred navigation technique.
We've made a couple of changes today to the Organization repositories listing to bring it a bit closer to the functionality of the GitHub.com Organization repositories tab. We now let you retrieve repositories which are forks of another repository, as well as those repositories which are sources (not forks).
# Grab all fork Repositories for an Organization curl "https://api.github.com/orgs/:org/repos?type=forks" # Grab all source Repositories for an Organization curl "https://api.github.com/orgs/:org/repos?type=sources"
Check out the docs for sorting and filtering options: