Page MenuHomePhabricator

Remove all "Phabricator Bot" code
ClosedPublic

Authored by epriestley on Apr 21 2017, 7:46 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 29, 5:26 AM
Unknown Object (File)
Thu, Nov 28, 12:17 AM
Unknown Object (File)
Mon, Nov 25, 4:04 PM
Unknown Object (File)
Wed, Nov 20, 9:55 AM
Unknown Object (File)
Sat, Nov 16, 2:52 PM
Unknown Object (File)
Mon, Nov 11, 8:32 PM
Unknown Object (File)
Thu, Nov 7, 11:30 PM
Unknown Object (File)
Mon, Nov 4, 6:10 PM

Details

Summary

Closes T7829 as wontfix. Closes T7965 as wontfix. Closes T7800 as wontfix. Closes T2731 as wontfix. Closes T1271 as wontfix.

We aren't maintaining this at all (see, e.g., T7829) and a user reported a technically accurate security issue via HackerOne: https://hackerone.com/reports/222870

Just throw it away until we get to the eventual Conphernece bot/API update and can do this stuff correctly.

Test Plan

Grepped for phabricatorbot.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Apr 21 2017, 7:46 PM
This revision was automatically updated to reflect the committed changes.

We use the bot quite heavily at my company. Is there anything stopping me from just copying the deleted code into a libphutil extension and continuing to use it? Really, PhabricatorBotLogHandler is what we care about most.

After 2.5 years of not upgrading because I didn't want to lose phabot, we finally have (went fairly smoothly yay). Is there a slightly less terse explanation for how I can do as @joshuaspence said? Or at least a pointer to the right documentation for such a project?

We use the bot quite heavily at my company. Is there anything stopping me from just copying the deleted code into a libphutil extension and continuing to use it? Really, PhabricatorBotLogHandler is what we care about most.

Thanks!