You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

sobolevn c1fa611f4d Adds an attempt to fix the CI Changes: 1. Fixes the licence information in the `plugin.zsh` to be MIT 2. Fixes link in the README 3. Fixes some tests Closes #54		7 years ago
.ci	Adds an attempt to fix the CI	7 years ago
.docker	added make distribution, updated travis and docker files	8 years ago
.github	Intallation instructions updated	7 years ago
man	Intallation instructions updated	7 years ago
src	Adds an attempt to fix the CI	7 years ago
tests	Adds an attempt to fix the CI	7 years ago
utils	Changing deb distribution name	7 years ago
.editorconfig	fixes after makefile crash	8 years ago
.gitattributes	fixes after makefile crash	8 years ago
.gitignore	refactored all src folder	8 years ago
.travis.yml	Adds an attempt to fix the CI	7 years ago
CHANGELOG.md	Version 0.2.1 release	8 years ago
CONTRIBUTING.md	This is a release commit.	8 years ago
LICENSE.md	CONTRIBUTING.md added	8 years ago
Makefile	fixes in finding functions, also test-make-ci added $PATH	8 years ago
README.md	Adds an attempt to fix the CI	7 years ago
git-secret.plugin.zsh	Adds an attempt to fix the CI	7 years ago

README.md

Unescape Escape

git-secret

What is `git-secret`?

git-secret is a bash tool to store your private data inside a git repo. How’s that? Basically, it just encrypts, using gpg, the tracked files with the public keys of all the users that you trust. So everyone of them can decrypt these files using only their personal secret key. Why deal with all this private-public keys stuff? Well, to make it easier for everyone to manage access rights. There are no passwords that change. When someone is out - just delete their public key, re-encrypt the files, and they won’t be able to decrypt secrets anymore.