Repository navigation
Add Brewfile.local and a Ghostty config.local for local overrides - #12
Merged
Merged
Conversation
Brewfile.local is ignored by git and installed after the Brewfile, so your own additions never conflict with `git pull`. Ghostty gets a `config-file = ?config.local` line after the repo's, so settings there override the repo's. CI installs a package from a Brewfile.local to prove it's picked up. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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.
Lets people customize the setup without editing tracked files, so
git pull && ./setup.sh(which the README recommends) doesn't run into merge conflicts.Brewfile.localis ignored by git. If it exists,setup.shrunsbrew bundleon it after the mainBrewfile, and its failures are listed at the end like the main Brewfile's. It only adds packages: dropping one of the repo's still means editing theBrewfile.config.local:setup.shaddsconfig-file = ?config.localright after the repo'sconfig-fileline. Ghostty loads included files in the order they're listed, so settings there override the repo's. The?makes the file optional, and the path is relative, so it resolves next to your Ghostty config. Existing setups get the line on their next./setup.sh.Brewfile.localwithbrew "hello"before the first run and checks that it got installed. The existing check that a second run changes nothing covers the new Ghostty line.Tested locally: the Ghostty step on a new config and on an existing one, run twice each. It added the line after the repo's, and the second run changed nothing. The
brew bundlepart only runs on macOS, so this PR's CI run is its test.🤖 Generated with Claude Code