ci: add PR-triggered CI workflow and CODEOWNERS#21
Merged
MrAlders0n merged 1 commit intodevfrom Apr 14, 2026
Merged
Conversation
Adds a new CI workflow that runs flutter analyze and flutter test on every PR targeting main or dev, and a CODEOWNERS file routing all review requests to @MrAlders0n. Combined with branch protection updates (require_code_owner_reviews), this enforces owner approval on every incoming PR before merge. The workflow uses least-privilege contents:read permissions and does not inject API_KEY, since analyze/test do not need it and keeping it out of PR runs prevents fork-PR exposure. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
.github/workflows/ci.yml— runsflutter analyzeandflutter teston every PR againstmainordev.github/CODEOWNERSrouting all review requests to @MrAlders0nWhy this is safe
permissions: contents: read(least privilege)pull_request(notpull_request_target) so PRs from forks run against PR HEAD, not baseAPI_KEY— analyze/test don't need it, keeps the secret invisible to fork PRsgithub.event.*data is interpolated intorun:steps (no injection surface)Follow-up (not in this PR)
Analyze & Testas a required status check onmainanddevTest plan
Analyze & Testjobflutter analyzepassesflutter testpasses🤖 Generated with Claude Code