Repository navigation
Enable configuration in gh (gh config) #622
Description
Activity
can we include aliases support?
@eddumelendez That's being tracked separately in #294.
@billygriffin does it warrant having a separate config for this? For instance, ghq does something similar by using a namespace within
git-config.If this were able to leverage that, then you'd also get everything else around it for free like having a hierarchy of global, user, per-directory settings as well as conditional includes.
To access the configs,
ghwould could dump and parsegit config --list --includes, usegit config --get ...on individual items, or use something likelibgitto access the config programatically.heya @thefotios . We explored that option and decided against it; in general we're trying to be very light in how we depend on
git. Given how far back we'd like to providegitsupport for and the wide varieties ofgitversions in the wild, we wanted a config system decoupled from any change ingit's config over time. That said, there are times when we do already take advantage ofgit configwhen it comes to branch configuration.
Describe the feature or problem you’d like to solve
A couple things have risen to the level of things where we feel like adding the ability to configure a set of preferences for
ghwould be appropriate.Proposed solution
Create a
gh configcommand (open to other ideas on the naming, but this is what we were thinking).Initially, this will include two preferences:
Our thinking is to have a config file, probably a yaml file, that contains these preferences and is where we read from when they use the tool. However, we'd also like a simpler and less error-prone way to change a particular preference, so we were thinking of:
gh config <key> <value>For example, to change your default editor, you could:
gh config editor vim(I don't know if this is exactly what the command would be, but that's the idea).Additional context
This is directly related to #546 and #308.