Repository navigation
Run analyze, format, and tests on every push and pull request - #12
Merged
Merged
Conversation
Issue #8's thread asked for CI on pull requests. The repo had no workflow, so regressions like the failing "the bug" test could sit unnoticed.
This was referenced Sep 15, 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
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.
Adds
.github/workflows/test.yml, which runs on every push tomainand on every pull request.Steps, matching what the package must already pass:
dart pub getdart analyze --fatal-warningsdart format --output=none --set-exit-if-changed .dart testAll pass on this branch locally on Dart 3.10.4: analyze reports no issues, format reports 0 of 7 files changed, and 26 of 26 tests pass.
This closes the CI request in #8's thread. That issue is about a test that was failing silently; a workflow like this is what would have caught it.