New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Make new configure file instead of git-config #21
Comments
Reasonable. I'll try on it later. Maybe
...or something, needs some consideration. |
In my opinion, there's no reason to continue using git-config format for ghq configuration. (excepting backward compatibility) What about using JSON or YAML format for the configuration? {
"root": "/path/to/ghqrepos",
"urls" : {
"https://ghe.example.com/" : {
"vcs": "git"
}
} root: "/path/to/ghqrepos"
urls:
https://ghe.example.com/:
- vcs: "git" |
If you do this, please use |
The "ghq" depends heavily on git, so I think it would be good to continue using gitconfig. I don't intend to add any more settings. |
Hi, @motemen,
Now ghq's configuration gets complex.
Currently ghq's configuration rents a space from git-config, but I think that it's a time to make the configuration file for ghq.
Have you thought about separating ghq configuration from git-config to another configuration file? (
$HOME/.ghqconfig
or something)The text was updated successfully, but these errors were encountered: