From e6ead54e9a67b131b7ae5b26bbb6dc27e7f14735 Mon Sep 17 00:00:00 2001 From: dwara001 Date: Wed, 30 Jul 2025 09:03:19 -0400 Subject: [PATCH] updated markdown to add script to remove existing gpg keys --- docs/how-to/git/add-user-to-git-secret.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/how-to/git/add-user-to-git-secret.md b/docs/how-to/git/add-user-to-git-secret.md index 87b4790b..9747d90a 100644 --- a/docs/how-to/git/add-user-to-git-secret.md +++ b/docs/how-to/git/add-user-to-git-secret.md @@ -93,6 +93,19 @@ in merge conflicts and more work figuring out what has actually changted. In your PR, please include the output of the `gpg {USERNAME}.gpg.asc` in the Pull Request text. +## Remove gpg keys for non existent users + +The below is an example. + +```script +git-secret reveal -f +cd init/git-secret +git-secret removeperson roy.d.ashley.jr@census.gov +git-secret removeperson patrick.o.ibekwe@census.gov +git rm ashle001*asc ibekw001*asc +./setup-git-secret.sh +git commit -m'remove ashle001 and ibekw001 gpg keys' -a +``` ## Using the updated encrypted files Once it is merged, you can inform the user, and they refresh and reveal in order to use the unecrypted files.