ci: use Vitest's --changed on non-main branches#1409
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
By the way, in order to request review from @flint-fyi/maintenance, I added the team under https://github.com/flint-fyi/flint/settings/access. And then started removing individuals. @barrymichaeldoyle informed me that gives people a kind of scary-looking "you were removed" email. So, I'll wait to keep doing that until people see this message. 😂 sorry if I alarmed you! |
.github/workflows/ci.yaml
Outdated
| path: | | ||
| .pnpm-store | ||
| node_modules/.vitest | ||
| - run: pnpm run build # ensures TS build output for correct test imports |
There was a problem hiding this comment.
I wonder if it's worth running only pnpm tsc -b here? As far as I understand, for Vitest tests we don't really need .js outputs, only .d.ts, right? Also, skipping tsdown build here would skip the expensive ATTW check.
cc @lishaduck
There was a problem hiding this comment.
OH! This just clicked for me. @barrymichaeldoyle I think you might have tried to tell me this when we paired 😂 - sorry if I steamrolled past you.
I had brain lapsed / forgotten that the current Vitest setup goes straight to .ts source. Without that knowledge, it would make sense that pnpm build is needed to get .js outputs. But with it, yeah, tsc -b for .d.ts files makes sense.
There was a problem hiding this comment.
Ok, right I forgot about vitest-dev/vitest#9353.
I couldn't get ts-patch to work in #1129 without using NODE_OPTIONS. I'll just use it I guess 🤷🏻♂️
|
60ba72d to
00d7ac1
Compare
|
Ok, so I did fix references. The failure now is that Vitest's That's why we used |
|
Lovely. Well, if that gets slow over time, we can always look into optimizing later. Thanks! This is very helpful. And it's cool to see issues filed upstream too. 🚀 |
|
@all-contributors please add @barrymichaeldoyle for infra.
|
|
I've put up a pull request to add @barrymichaeldoyle! 🎉 |
Adds @barrymichaeldoyle as a contributor for infra. This was requested by JoshuaKGoldberg [in this comment](#1409 (comment)) --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
PR Checklist
--changed) #1332status: accepting prsOverview
Uses the implementation proposed by @barrymichaeldoyle in #1332 (comment).
Note that all tests are re-run in this PR because it changes configs from
main. But future PRs should ™️ nicely re-run only impacted ones.Co-authored-by: @barrymichaeldoyle
❤️🔥