web-platform-tests / web-platform-tests/rfcs
Do we still need the merge_pr_* tags?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 110
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
Historically we had to have the merge_pr_* tags to have somewhere to put the generated manifests.
This isn't actually true any more, now that we're using GitHub Actions for them, as we can simply pull them down as workflow artifacts.
It's unclear whether https://docs.github.com/en/rest/actions/artifacts?apiVersion=2022-11-28#list-artifacts-for-a-repository alone suffices, as that doesn't have a defined sort order, or we can simply do what we do now and start querying commits to see if we have a workflow run for them.
It would be nice to clear out the 32927 merge_pr_* tags we currently have, as this is pretty noisy when pulling.
See also: #117.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked #117 and the GitHub Actions artifacts API documentation referenced in the issue. Compare listing workflow artifacts with querying commits for workflow runs, then define how generated manifests should be retrieved and whether the 32927 merge_pr_* tags can be removed. Done means the replacement approach and tag cleanup are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100