Skip to content
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

Configure commitizen.json location - MacOS #339

Closed
pappalar opened this issue Aug 29, 2016 · 3 comments
Closed

Configure commitizen.json location - MacOS #339

pappalar opened this issue Aug 29, 2016 · 3 comments

Comments

@pappalar
Copy link

As #240 states, the commitizen.json is saved in the home folder, which is quite annoying.

I have not found any way to change that.

If there is just a configuration to set, it would be interesting to write a README section about it.

@jimthedev
Copy link
Member

@racer1988 Can you expand on what is annoying about the file being in the home directory? The current leaning is to move commitizen.json into .commitizen.json so that it is hidden. Is there some other use case where it should be in the node_modules folder instead?

@pappalar
Copy link
Author

It is fine also to add the dot in front so it will be hidden.

However to avoid future changes again, I would tend to think we align to many other command line tools by creating a folder called .commitizen and add the cache file inside.

This way we can use the folder for many more configuration if needed.

(examples of config/cache folders are .subversion, .config for git, .iterm2, .vim, .gem, .dropbox., .cocoapods, .npm, .m2, android, .wireshark, .gnupg, .cordova etc etc etc..)

malept added a commit to malept/cz-cli that referenced this issue Dec 11, 2016
malept added a commit to malept/cz-cli that referenced this issue Dec 15, 2016
jimthedev pushed a commit that referenced this issue Dec 15, 2016
…f home-or-tmp (#400)

* feat(commit): use OS-specific cache dir for commitizen.json instead of home-or-tmp

Based on #252.

Fixes #240, #252, #339

* refactor(tests): replace rimraf with fs-extra
@jimthedev
Copy link
Member

Closed by #400. You can now delete the commitizen.json. We might need to add a command line alert if this file is found that it is now safe to delete that file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants