Skip to content

Ignore fvm files - #1042

Open
rickdijk wants to merge 1 commit into
mainfrom
chore/fpl-10-gitignore-fvm
Open

rickdijk wants to merge 1 commit into
mainfrom
chore/fpl-10-gitignore-fvm

Conversation

@rickdijk

Copy link
Copy Markdown

✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)

Repository hygiene. Two lines in .gitignore, nothing else.

⤵️ What is the current behavior?

.fvmrc and .fvm/ are not ignored. fvm is a local SDK manager some maintainers use; nothing in this repository requires it, and CI does not use it. The workflows install Flutter with subosito/flutter-action@v2 on the stable channel.

That means the first time someone runs fvm use in a clone here, the resulting .fvmrc shows up as an untracked file and can be committed by accident. One maintainer's local SDK choice would then become everyone's, including contributors who do not have fvm installed.

Baseflow/flutter_cache_manager already ignores both paths. This repository and Baseflow/octo_image did not.

🆕 What is the new behavior (if this is a feature change)?

.fvmrc and .fvm/ are ignored, added to the Miscellaneous block to match where flutter_cache_manager has them. A local SDK pin stays local.

💥 Does this PR introduce a breaking change?

No. Neither path exists in this repository today, so nothing is removed from tracking and no working tree changes.

🐛 Recommendations for testing

git check-ignore -v .fvmrc .fvm/flutter_sdk matches both rules. git status is unchanged for anyone without fvm.

📝 Links to relevant issues/docs

Linear FPL-10. Same change in Baseflow/octo_image under FPL-11, and Baseflow/flutter_cache_manager PR 524 removes the matching docs that presented fvm as a requirement.

🤔 Checklist before submitting

  • All projects build
  • Follows style guide lines (code style guide)
  • Relevant documentation was updated
  • Rebased onto current develop

🤖 Generated with Claude Code

fvm is a local SDK manager some maintainers use. CI installs Flutter
directly and nothing here requires it, so a pinned SDK should never be
committed. flutter_cache_manager already ignores these; this repo did
not, so a stray `fvm use` would have checked one in.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant