docs: clarify that flint init works with existing mise.toml#208
Merged
zeitlinger merged 2 commits intografana:mainfrom Apr 23, 2026
Merged
docs: clarify that flint init works with existing mise.toml#208zeitlinger merged 2 commits intografana:mainfrom
zeitlinger merged 2 commits intografana:mainfrom
Conversation
Signed-off-by: Gregor Zeitlinger <[email protected]>
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies in the README that flint init is intended to be used even in repositories that already have an existing mise.toml, reducing confusion about “manual edits vs init” setup paths.
Changes:
- Adds explicit guidance that
flint initis appropriate for repos with an existingmise.toml - Notes that users can trim the generated tool list after running
flint init
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
zeitlinger
changed the title
martincostello
approved these changes
Apr 23, 2026
Signed-off-by: Gregor Zeitlinger <[email protected]>
Merged
zeitlinger
pushed a commit
that referenced
this pull request
Apr 23, 2026
### Added - group linter renovate updates ([#209](#209)) ### Fixed - expand baseline guards for config and flint changes ([#215](#215)) - remove stale exclude_paths init placeholder ([#211](#211)) - baseline lint coverage changes ([#214](#214)) - align biome init and formatter ownership ([#205](#205)) ### Other - *(deps)* update dependency npm:renovate to v43.133.0 ([#216](#216)) - *(deps)* update dependency npm:renovate to v43.132.2 ([#212](#212)) - *(deps)* update taiki-e/install-action digest to 5f57d6c ([#204](#204)) - clarify that flint init works with existing mise.toml ([#208](#208)) - guard against overlapping fixer ownership ([#206](#206)) > [!IMPORTANT] > Close and reopen this PR to trigger CI checks. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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
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
Clarify that
flint initis appropriate for repositories that already usemise, not just greenfield setup.Why
The current installation section can read like there are two separate paths:
flinttomise.tomlflint initThat can imply
flint initis mainly for new repositories, while manual edits are the safer choice whenmise.tomlalready exists.This change makes it explicit that
flint initis still appropriate in a repo with an existingmise.toml, and that users can trim the generated tool list afterward.Testing
mise run lint