Page MenuHomePhabricator

Renamed tool diffusion repository failed to be updated in toolsadmin.wikimedia.org
Closed, DeclinedPublicBUG REPORT

Description

List of steps to reproduce (step by step, including full links if applicable):

What happens?:
Diffusion repository link on toolsadmin.wikimedia.org stays unchanged, and the status is shown as "Unknown". For me, I create a repo for my tool satori, then rename the repo on Phabricator to crystal.

What should have happened instead?:
It should be updated.

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc.:
I made some special configuration for this repo - to make it just a mirror (observer) of a GitHub repository. Don't know if this is relevant.

Event Timeline

How would/should/could Striker know that you renamed the repository with a direct management workflow?

I thought maybe Phabricator has such interface to lookup the rename action..?
And another problem is when I rename it back to the original name (tool-blah), info displayed on toolsadmin does not refresh, maybe could add such function to "refresh" it.

bd808 edited projects, added Striker; removed Toolforge.

I am going to close this as declined as any work on Striker for git repos should really be put into T296893: Replace Diffusion integration with Gitlab integration in Striker (toolsadmin) at this point. I also don't think we will ever put in the effort to find a way to track arbitrary changes made from external workflows. The change history at https://phabricator.wikimedia.org/source/crystal/manage/history/ shows manual changes to just about everything that Striker originally setup. This is fine by policy, but not something that is considered "supported" as a workflow.