search

drewblessing / gitlab-cli

GitLab Command Line Tool - Interact with your GitLab server via the command line to manage snippets, projects and more.
MIT License
166 stars 20 forks source link

Create a config file in $HOME folder instead of using config.yml #17

Closed genewoo closed 11 years ago

genewoo commented 11 years ago

I'd like to share my setting across folders. Maybe a file in $HOME folder is a much better place to hold it.

Or, we can consider to create custom config in .gitconfig, since every gitlab user is a git User.

BTW, I had a set of scripts on GitLab, maybe I can create several pull requests.

dblessing commented 11 years ago

Hi @genewoo. Absolutely, this is a great idea. I have worked this into my refactoring for when I package a gem. It will be part of https://github.com/drewblessing/gitlab-cli/issues/13

I also welcome any pull requests for adapting the scripts you've created in the past. Thanks!

dblessing commented 11 years ago

Merged for 2.0.0. It will look for .gitlab.yml file in user's home directory.

dblessing commented 11 years ago

@genewoo Please be advised - I changed the config file from ~/.gitlab.yml to ~/.gitlab_cli.yml for the actual release. This makes more sense long-term. Thanks.

genewoo commented 11 years ago

if we are going to use gitlab as binary execute file, I would suggest .gitlab.yml, it's kind of convention. So far, I don't heard gitlab need a local configure file, so in my opinion, .gitlab.yml is safe.

Best Regards,

Gene Woo

On Mon, May 13, 2013 at 3:56 AM, bke-drewb notifications@github.com wrote:

@genewoo https://github.com/genewoo Please be advised - I changed the config file from ~/.gitlab.yml to ~/.gitlab_cli.yml for the actual release. This makes more sense long-term. Thanks.

— Reply to this email directly or view it on GitHubhttps://github.com/drewblessing/gitlab-cli/issues/17#issuecomment-17784247 .

drewblessing commented 11 years ago

Point well taken. I reverted this. Thanks for your input.