Quality-gate inventory #46
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TheAnachronism/tt-rss-viewer#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #41
Question
What automated quality checks exist today for this repo (Forgejo workflows, nix/flutter local commands, analysis_options), and what do current Flutter/Android release practices typically gate on before a beta? Facts only — primary sources and this repo's config.
Resolution
Gist: The repo has runnable local primitives (
flutter analyze, 34-file/139-testflutter test, and a release APK build), but its only Forgejo automation is the post-tagalpha/*packaging/upload workflow. There is no PR or pre-tag CI gate, and analysis, tests, format, Android lint, coverage, integration/device checks, install smoke, dependency/security checks, and artifact/signature verification are not automated. Flutter/Android primary sources commonly cover analysis, layered tests/coverage, release-artifact testing, signing/versioning, lint, and device quality; Play testing tracks/pre-launch reports are store-only comparisons for this sideload beta.Committed on branch
research/quality-gate-inventoryatec8ac58:docs/research/quality-gate-inventory.mdCI policy remains explicitly deferred to #47.