Commit generated analyzer excludes and regenerated mocks - #123
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
Two generated-file updates produced by running
makelocally.analysis_options.yaml: the Flutter tool rewrites this on everyflutter build linux, adding ananalyzer.excludeblock forbuild/and the platform directories. Committing it stops the file from reappearing as a dirty working-tree change after each build.test/app_launch_test.mocks.dart: regenerated bydart run build_runner build -dvia theautogentarget. Mockito dropped its version stamp from the header and added anexperimental_member_useignore.No hand-written code changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_012R5AzYAqAGjwjueMswUHk6