In T158739#3250723, @Framawiki wrote:

It will be very useful for projects like Huggle.
I would like to work on this, by create a Python bot.

Great if you would take this on! It is something we would need for a couple of our projects as well we just never get around to building it =)

Some research:

• https://github.com/carlos-jenkins/python-github-webhooks can be used to catch github webhook and execute a script with parameters
• https://github.com/disqus/python-phabricator phabricator library, can really easily create a comment on a task : phab.task_comment(task, msg)
• https://github.com/kakaroto/github_to_phabricator/tree/master/wmfphablib sample of the use of the previous

https://phab-01.wmflabs.org/p/Github-notif-bot/

>>> phab.maniphest.edit(objectIdentifier='T183', transactions=[{'type':'comment', 'value':'valeur'}, {'type':'projects.add', 'value':['Patch-For-Review']}])

:-)

Templates:

• PR created
• PR merged
• commit pushed

I'll work on "PR created" first.

Templates for @gerritbot : https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/gerrit/files/etc/its/templates/

I'll now create tasks in Github-notif-bot project and continue to make general reports here.

WMDE, especially the WMDE-FUN-Team might be interested in this as well.

Unfortunately I'm no longer planning to work on this topic. In particular, now that we have a Wikimedia Gitlab instance, I don't see reasons to still use Github.

In the meantime, a similar account has been created by @rook under the account @github-toolforge-bot.

I note that @GitHubPRBot and @github-toolforge-bot both exist, but clicking on their profiles, I don't see links to their repos or instructions for how to sign up to use them for one's own GitHub repos. Is one of these bots usable by the public (which would resolve this ticket, just need to document it better)?

cc @Dbrant, @rook

To use github-toolforge-bot, a workflow needs to be created in the github repo (see https://github.com/toolforge/quarry/blob/main/.github/workflows/notification.yaml). An API token for the bot's phab account needs to be stored on GitHub Secrets (as TOOLFORGE_PHAB_BOT_KEY in this example). I assume a new token should be used for each github repo, and phabricator admins can generate these tokens on request.

Nice. If this solution is public / open to all developers, I'd recommend documenting the process somewhere (on a wiki page? in a repo as a README?), linking to it in the bot's phab profile, then closing this ticket as resolved.