-
Notifications
You must be signed in to change notification settings - Fork 36
RFC: Run skuba upgrades in test CI environments #2173
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 69f2ea6 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Why do we
would swapping the order be bad? |
I will defer that to @72636c |
zbrydon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy with this before/if we investigate/commit to a potentially parallel lint and test command that reports errors in both.
Our templates currently advocate for running tests before lint.
This is problematic if we want to introduce runtime changes to the
testinterface as when theteststep fails thelintstep won't be run. This will be especially problematic when we switchJestout forvitestbecause everything will break.I propose running skuba upgrades in CI when running
skuba test