-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
Labels
CI/infraRepo CI & infrastructureRepo CI & infrastructureadminAdministrative issues that need to be addressed by a maintainerAdministrative issues that need to be addressed by a maintainere1-hoursEffort: < 8 hrsEffort: < 8 hrsp2-mediump3-lowtriage:acceptedIssue has been accepted and a PR can be createdIssue has been accepted and a PR can be created
Description
We should consider setting up a workflow to execute npm run test-and-fix and commit results, so as to minimize the likelihood of our contributors being told to keep their PRs focused to their own changes, like #6585 (comment). /cc @svrnm
Edit 2025/06
Here's what I think we need two reusable actions (such as these actions from our repo) to do the each of the following (as separate actions):
- Apply any
npm run XXXscript (un trusted), and creates a patch files - A reusable action (trusted), that can create a PR from a patch file
Create another action, or just a script to run test-and-fix, using the two actions previously mentioned.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
CI/infraRepo CI & infrastructureRepo CI & infrastructureadminAdministrative issues that need to be addressed by a maintainerAdministrative issues that need to be addressed by a maintainere1-hoursEffort: < 8 hrsEffort: < 8 hrsp2-mediump3-lowtriage:acceptedIssue has been accepted and a PR can be createdIssue has been accepted and a PR can be created
Type
Projects
Status
No status