wikiphabot should import/respect the rules we've written over the years for wikibugs (what bug updates go to which channels).
|· · ·|
|Resolved||• yuvipanda||T131 IRC bot to report Phabricator activity exactly like Wikibugs does with Bugzilla|
|Resolved||valhallasw||T324 Have wikiphabot follow the same channel announce rules as wikibugs|
|· · ·|
- Mentioned In
- rTWBTec8ba19f7171: Merge pull request #1 from valhallasw/master
T131: IRC bot to report Phabricator activity exactly like Wikibugs does with Bugzilla
T571: Make wikibugs parse phab emails & send messages
- Mentioned Here
- T131: IRC bot to report Phabricator activity exactly like Wikibugs does with Bugzilla
T763: Phabricator far too spammy and off-topic to continue posting to wikibugs-l
T43: Decide how to organize projects
The notifications are handled by PhabricatorBotFeedNotificationHandler:
Naming of tags will be: (from T43#5660)
|Bugzilla product||Bugzilla component||Phabricator project|
|Wiki Loves Monuments||Unused images||Wiki_Loves_Monuments-Unused_images|
I think it would make more sense to configure this directly in phabricator:
We could add a custom field to projects called "irc channel" which would be used to associate a project with a channel.
Then any updates to tickets in a given project would get posted into the relevant irc channel automatically.
In addition to this it would be nice if we had a way to specify the types of notifications that get filtered, on a channel-by-channel basis, but for starters a simple project filter would suffice.
Well, that didn't work. https://github.com/legoktm/phabricator/commit/7b93dd1bb9eae1a350e52d691a2ddfbaddc44dac is how far I got.
I'm not really sure if it's a good idea to hack on the code directly or if there's a preferred way to extend it.
@Legoktm one way to approach this would be to fork the message handler class ( or subclass/extend it ), that way our changes are mostly isolated to a separate file and hopefully don't cause too much maintenance headaches if we have to maintain our own custom handler outside of the upstream.
for the format, although those do not seem to be the current rules. In any case, the actual rules should be in git before Day 1.