Add fixture metadata triage workflow#5653
Conversation
FloEdelmann
left a comment
There was a problem hiding this comment.
Good idea! If this works fine, we could try to introduce more validations (maybe using the fixture-valid test results) as automatic workflows.
Co-authored-by: Flo Edelmann <git@flo-edelmann.de>
|
@FloEdelmann It looks like the run failed because it needs a token setting. I had naively assumed it would be set automatically like |
|
I set it now using |
|
@luc122c so the "dry-run" actually commented on one PR (#5657) and labeled some others, even if it shouldn't 😬 See its own output:
So it sorta useful. It should ignore PRs with any link though (a video or forum post in But: Given that …
… it sure sounds like this needs a lot of tweaking to be useful. At least it seems to consume only one premium request, but that is bound to change soon, too. |
|
Yes, I'm quite dissapointed with how that turned out! 🤣 I realised the 100 limitation, but thought that wouldn't matter too much once it had started clearing the backlog a bit. It's weird that it only commented on one. And it wasn't even related to the PR. I would have expected what it wrote to be in the report instead. I think the dry-run input did work for the labels, I don't see the 'incomplete' label on any of those PR's. But yet it still commented. Hmm. I'll open a PR to disable the 'daily' trigger so it's only manually triggered for now. Yes, it seems like it does need a lot more work for it to be useful. I just seen this video that also discusses the changes to the GitHub Copilot pricing! It seems like they're essentially removing all the value from their offer. |
|
Also, I don't know if this affected the AI's search but it's making it very difficult for me right now! https://www.githubstatus.com/incidents/ql942tw29yl6 |
|
These ones were labeled as
From here on, the workflow failed to apply the label:
|
Summary
Adds a daily GitHub Agentic Workflow to triage PRs with
new-fixtureandvia-editorlabels, checking for missing required metadata in fixture JSON files.What it does
new-fixtureANDvia-editorlabelsincomplete"$schema": ".../schemas/fixture.json"links.manualORlinks.productPageexistsincompletelabel and posts comment if both are missingSchedule
Runs daily (can also be triggered manually)
Labels required
This workflow needs the following label to exist in the repository:
incomplete(already exists)Note: The workflow also supports a dry-run input when triggered manually - it will report what would be done without making changes.