Repo missing from standardized table

[johanneskoester]

The repo https://github.com/GuttmanLab/chipdip-pipeline does not occur in the standardized workflows table. This reflects the state of data.js.
However, by now, the repo seems to be standardized correctly, as this test (message at the end) suggests:
https://github.com/snakemake/snakemake-workflow-catalog/actions/runs/15581178162/job/43876595470

@m-jahn, any idea what's happening here?

[m-jahn]

Hi Johannes, indeed a strange case. I checked this repo with a local test run and it does get listed as "standardized". At its previous version (the one that is now in the catalog) it is present in non-standardized workflows. What likely happened is that the recent update of this repo was not captured by the catalog because there was a break when building failed on github. This failure was a problem on the github action server side, not ours.
However, on the next update or release of the repo it should be included as standardized. There does not seem anything wrong with it.

[bentyeh]

Hello, thank you for opening this issue. Looking at the Actions history, it seems like the catalog has been re-generated and deployed a couple times since @m-jahn's comments, but the chipdip-pipeline repo still does not show up as a standardized workflow (and the last update date is incorrect - it shows up as 2025-05-16 in the catalog, even though the last release was on 2025-05-20).

Any update would be appreciated!

[m-jahn]

@bentyeh I wrote before:

However, on the next update or release of the repo it should be included as standardized. There does not seem anything wrong with it.

So let me briefly explain why this happens. Not the catalog, but your repo needs to be updated to force an updated entry in the catalog. I understand that there is a discrepancy already now between the version in the catalog and the current version of your repo. However this is not enough to trigger an update of your repo in the catalog build action. The reason is that the catalog build action is automatically running every week on Monday morning, and it will only test repos that had changes as recent as the past 7 days. So every week, the most recent changes are included. In your case I suspect that your repo fell in a period where the build action failed, with the result that we missed changes of repos from 7 days, until the next build action was triggered. There are two options to remedy:

1. just wait until you make the next update/release of your repo, and it will be automatically updated in the catalog
2. I run an update of the catalog locally and include your repo in dedicated pull request

Personally I feel option 1 is much less of a hassle. If you however plan to not change your workflow for a long time we can go for option 2.

[bentyeh]

Thank you for the clarification, and I apologize for my misunderstanding! (I mistakenly thought that "repo" in "on the next update or release of the repo" referred to the snakemake workflow catalog, but you were referring to the chipdip-pipeline repository!)

I plan on releasing an update soon, so fingers crossed it gets automatically included in the catalog!