put `.gitsecret` in version control? #39

Closed
techhazard opened this Issue Jun 23, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@techhazard

The usage guide currently does not mention at all if the .gitsecret directory should be put in version control or not.

Perhaps it would be a good idea to mention that?

@sobolevn

This comment has been minimized.

Show comment
Hide comment
@sobolevn

sobolevn Jun 23, 2016

Owner

Hi, thanks for your feedback!

Well, as I see it is quite a common question: #14 (comment)

I will put the note into the readme.

Owner

sobolevn commented Jun 23, 2016

Hi, thanks for your feedback!

Well, as I see it is quite a common question: #14 (comment)

I will put the note into the readme.

@sobolevn sobolevn added this to the version 0.3.0 milestone Jun 23, 2016

@sobolevn sobolevn self-assigned this Jun 25, 2016

sobolevn added a commit that referenced this issue Jul 10, 2016

This is a release commit.
Changes:
1. Now everything is tested inside the `docker`-containers and `OSX` images on `travis`.
2. We now have `CONTRIBUTING.md` and `LICENSE.md`. `README.md` is also changed.
3. We have a brand logo.
4. We have autodeploy to `bintray`.
5. Everything is `shellcheck`ed (except `tests/`).

Closes #32 #33 #34 #35 #39

@sobolevn sobolevn closed this Jul 10, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment