Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Request]: Run flutter analyze workflow in proper scopes and enforce its results

Open
#2,775 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart
Domain
ci-cd

Research direction

Start by locating the CI workflow that runs flutter analyze for all plugins and inspect how changed scopes are determined. Compare the workflow behavior for a plugin-only change, then verify that analysis is limited to affected packages and that analyzer warnings cause the relevant CI check to fail.

Written by the indexing model from the issue text.

Description

enhancement triage
Plugin

All

Use case

It makes no sense to run analyze on all packages in every PR.

Here is an example where in PR with device_info_plus files changes only I see warnings for another plugin, because the analyze task runs for all plugins:
Screenshot 2024-03-30 at 15 13 29

Proposal

Suggest to do multiple changes:

  • Run analyze only in the scope of changed files in PRs.
  • Make analyzer warnings failing the set of CI checks to enforce issues resolutions, instead of catching up with fixes later as we do now.
Dominant language
Dart
Stars
1.9k
Forks
1.3k
Avg merge
6d 16h
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluttercommunity/plus_plugins

All issues in fluttercommunity/plus_plugins

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.