Improve CI times and make merge queue only trigger one CI run#3755
Merged
TrueDoctor merged 16 commits intomasterfrom Feb 18, 2026
Merged
Improve CI times and make merge queue only trigger one CI run#3755TrueDoctor merged 16 commits intomasterfrom
TrueDoctor merged 16 commits intomasterfrom
Conversation
1b1889e to
377349f
Compare
timon-schelling
approved these changes
Feb 18, 2026
Member
timon-schelling
left a comment
There was a problem hiding this comment.
LGTM, we could do dev builds for PRs and only release builds on master
Member
Do you mean for build links? I think we should always use release optimizations for build links. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
• Splits
rust-fmtinto a separate job so authors get feedback on their PRs more quickly• Frontend linting can't easily be split the same way since the linting depends on the wasm module to be present
• Removes the explicit build step from the ci pipeline (we should catch the build failures in the other phases)
• Splits the action into two separate ones, one for the deploy when pushing to master and one for regular ci jobs
• Don't run the entire rust build for pushes to master, these have been checked in the pr beforehand. When force pushing to master manually, the authors should test that their code compiles themselves, that is not what the ci is for.
• Adds the skip-merge-queue action to avoid running the ci twice when a merge queue is used