Skip to content
Jump to bottom

updated markdown to add script to remove existing gpg keys #256

Merged
merged 3 commits into from
Aug 1, 2025
Merged

updated markdown to add script to remove existing gpg keys #256

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e6ead54
updated markdown to add script to remove existing gpg keys
Jul 30, 2025
29a5c72
updated markdown to add script to remove existing gpg keys
Jul 30, 2025
e4f7453
updated markdown to add script to remove existing gpg keys
Jul 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
15 changes: 14 additions & 1 deletion docs/how-to/git/add-user-to-git-secret.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# How to add a user to git-secret
# How to add/remove a user to git-secret
dwara001 marked this conversation as resolved.
Show resolved Hide resolved

This describes the steps to add a user's GPG key to the main `support` keyring, as well as how to add it to the
`git-secret` setup in each account.
Expand Down Expand Up @@ -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
dwara001 marked this conversation as resolved.
Show resolved Hide resolved

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.
Expand Down