-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
chore: formatted files with Prettier via trunk fmt #19355
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
chore: formatted files with Prettier via trunk fmt #19355
Conversation
✅ Deploy Preview for docs-eslint canceled.
|
1aa2803
to
b236d70
Compare
b236d70
to
351648d
Compare
351648d
to
207fa32
Compare
207fa32
to
3b480ce
Compare
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
@fasttime reminder that when you remove the "stale" issue also leave a comment explaining why this isn't stale. |
Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update. |
Ping @JoshuaKGoldberg |
The second half of the day Tuesday (tomorrow) and the first half of Wednesday I'm fully clear (all EST). |
Okay, let me see if I can get in touch with everyone to coordinate. |
Let's do Wednesday, March 19, at 10am EDT? When you start, please post in Discord and add a comment to each open PR not to merge until you give the all-clear. And when completed, also post in Discord and on the PRs. I should be online around that time barring unexpected circumstances. |
Reminder: we should probably add |
Great work! |
This comment was marked as outdated.
This comment was marked as outdated.
Also, is it a typo on this line? Line 61 in 46eea6d
- --flter
+ --filter |
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain: internal tooling change
Fixes #17814 (part 2 of 2).
What changes did you make? (Give an overview)
Builds on top of #19354 by additionally:
npx trunk fmt --all
.git-blame-ignore-revs
tooThe CodeQL reports are all for existing code so I dismissed them. This PR shouldn't change any behavior or impact users in any way. Any actual configuration changes should all be in #19354.
Is there anything you'd like reviewers to focus on?
When on the github dot com view, I would recommend viewing with Hide whitespace enabled.
The intended merge order of PRs to avoid
main
branch CI failures is:.git-blame-ignore-revs