web-platform-tests / web-platform-tests/interop
Avoid unintended scope changes to active focus areas
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Maybe we should have a CI check (in wpt) to avoid test changes for tests in interop-* (for active focus areas). Require a commit message to link to an issue in the interop repo?
c.f. https://github.com/web-platform-tests/interop/issues/345 , https://github.com/web-platform-tests/interop/issues/338
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 issue and the referenced interop issues 345 and 338, then inspect how CI currently validates changes to interop-* tests. Define the check's scope and the required commit-message link behavior; done means unintended changes to active focus areas are rejected unless they reference an issue in the interop repository.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100