-
Notifications
You must be signed in to change notification settings - Fork 132
revisit prettier automation #2470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
In light of https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised (though we luckily don't use tj-actions/changed) perhaps we should reconsider using a third party action. |
Discussed at editors' meeting today https://www.w3.org/2025/03/26-aria-editors-minutes.html#475b |
We want to explore formatting after merge. While there is a chance of introducing merge conflicts, it seems fairly unlikely that formatting will add unexpected merge conflicts - the expectation is that formatting only affects lines that were changed. @daniel-montalvo I realized it would cause unnecessary respec builds from main. How much of a concern is that? |
Partially addressed in #2536 Still pending is how to handle forks more properly. We are now just throwing an error, which is not very helpful. |
Discussed today at the editors' call https://www.w3.org/2025/05/28-aria-editors-minutes.html We're leaning towards switching to a custom action. We also want to additionally run that action on commits to main, so that PRs from forks get fixed upon merge. |
In #2464 I had re-activated prettier after it had been disabled in #2307.
I don't know if the dry-run option was really relevant. But it disabled the automation and didn't surface the errors. I don't think that was what we wanted.
I'm not sure if the dry-run option was necessary. It looks to me that the failure should be caught by handle-commit-failure anyway?
If it was, then we could change the action to run prettier on commits to main (instead of on PRs).
Alternatively, we could give up on automated formatting and just use dry-run, but surfacing errors (which authors then need to fix).
Or there are other ideas.
The text was updated successfully, but these errors were encountered: