Today PendingChangesBot at https://phabricator.wikimedia.org/project/manage/8239/ was created, however https://github.com/zache-fi/PendingChangesBot/issues also exists, so there are two issue trackers now.
Do you plan to switch off one of them to avoid duplication and fragmentation?
Description
Description
Related Objects
Related Objects
- Mentioned Here
- T406325: Howto setup development environment
Event Timeline
Comment Actions
[FWIW, judging by T406325: Howto setup development environment, it seems like https://github.com/Wikimedia-Suomi/PendingChangesBot-ng might be the current repo for the project.]
Comment Actions
Uhm, in that case it's still a problem per https://github.com/Wikimedia-Suomi/PendingChangesBot-ng/issues
@Zache: Can you please clarify which one issue tracker to use? Thanks.
Comment Actions
We moved most Outreachy tasks to using PendingChangesBot-ng/issues to reduce duplicate work on tickets. So, most, if not all, microtasks are in GitHub, and I think that I could start to close these. However, there are still tickets which I will keep on Phabricator as they are related to other projects which are using Phab. Most notably, Pywikibot + Gerrit, which will require Phab tickets.
Comment Actions
@Zache Random idea (which might not be suitable here, but I thought I'd suggest it just in case) — if GitHub issues will be the primary location for tasks about PendingChangesBot, but there are some tasks for (other) projects in Phabricator that affect/are related to PCB, maybe the current project could be renamed/repurposed to something like an tag?
Comment Actions
So far we've interpreted #affects-foo as an issue in another codebase than foo. I'm okay'ish with the comment, thus I'm going to decline this for now...