Revert #1278 (Add build.mill setup)#1387
Merged
Merged
Conversation
3 tasks
timsueberkrueb
approved these changes
Apr 24, 2026
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
2 participants
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.
We had hoped that using
millwould help with the spurious CI failures, but it doesn't seem to have done so.Now we're in a state where we have two increasingly inconsistent ways (see the bug I fixed in
build.sbt?) of building the project, running tests, etc.Let's cut our losses and remove Mill (revert #1278).
I'm fine with keeping Mill if somebody actually uses it, but it currently feels like it only exists to cause me more work (in the context of changes like #1386).
For the record, I'd be fine with replacing sbt by Mill altogether, but I'm not sure how other team members feel about this.