epriestley bdbe9df65e Remove support for GitHub post-receive notifications ... Summary: - These never actually did anything. - I don't even really remember why I built them, maybe the Open Source team was pushing for more GitHub integration or something? I really have no idea. - Anyway, repository tailers do everything these could do (and much more). Test Plan: - Ran tailers off GitHub for many months without needing post-receive hooks. - Grepped for relevant strings, couldn't find any references. - Used "Repository" edit interface for a Git repository. Reviewers: btrahan, jungejason Reviewed By: jungejason CC: aran, jungejason Maniphest Tasks: T706 Differential Revision: https://secure.phabricator.com/D1273		2011-12-24 09:00:08 -08:00
..
applicationconfiguration	Automatically redirect 404's that wouldn't be 404s if they had a trailing slash	2011-04-04 10:29:46 -07:00
console	Move event framework from Phabricator to libphutil	2011-11-16 16:34:45 -08:00
controller	Modularize oauth.	2011-02-27 20:38:11 -08:00
default	Remove support for GitHub post-receive notifications	2011-12-24 09:00:08 -08:00
exception	Fix conservative CSRF token cycling limit	2011-07-14 08:09:40 -07:00
mapper	Import some code, some of which may be relevant to the project.	2011-01-17 19:31:39 -08:00
request	Add diff view for Maniphest Task "description changed" transactions	2011-12-08 18:15:19 -08:00
response	Add X-Frame-Options for all response	2011-09-14 10:43:24 -07:00
writeguard	Create AphrontWriteGuard, a backup mechanism for CSRF validation	2011-08-16 13:29:57 -07:00