Repository navigation
feat(btw_client): Fall-through client settings to user-level btw.md - #112
Merged
Merged
Conversation
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.
Fixes #111: project-level and user-level
btw.mdfiles now work together, allowing users to define global defaults in~/btw.mdwhile keeping project-specific rules in their project'sbtw.md.How are settings merged?
When both project-level and user-level
btw.mdfiles are present, settings are merged according to the following rules:clientandtoolstake from project-level first, then user-levelbtw.md.optionsare merged, with project-level values taking precedence over user-level values