Repository navigation
Conversation
PR HealthPublish ✔️
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. This check can be disabled by tagging the PR with Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with Breaking changes ✔️
This check can be disabled by tagging the PR with API leaks ✔️The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.
This check can be disabled by tagging the PR with Unused Dependencies ✔️
For details on how to fix these, see dependency_validator. This check can be disabled by tagging the PR with License Headers ✔️
All source files should start with a license header. Unrelated files missing license headers
This check can be disabled by tagging the PR with Coverage ✔️
This check for test coverage is informational (issues shown here will not fail the PR). This check can be disabled by tagging the PR with |
|
Closing in favor of re-enabling the existing upstream |
Motivation
The monorepo's generic
Health / coveragecheck can report success even when a newly added Dart test fails to load. This happened on csslib PR #2 with an unresolvedPageDirectivetype; the Health check stayed green despite a Dart compilation error in its logs.Scope
dart pub get,dart format --set-exit-if-changed,dart analyze --fatal-infosanddart test --platform vminpkgs/csslib, failing the job on any command error.QA
This is an independent verification gate, not a replacement for regression tests. Check the Actions run on this PR before marking ready. Existing csslib workflow may require enabling in the fork's Actions settings.