If you make changes to this website on GitHub.com's web editor directly, you shouldn't have to worry about this. If you are developing locally and/or are a long-term website editor (who should probably be developing locally!), consider these recommendations.
Enable SSH Key Commit Signing¶
You can use an existing SSH key for signing, or create a new one.
- Configure your Git client to sign commits and tags by default (remove
--globalto only sign by default for this repo):
git config --global commit.gpgsign true git config --global gpg.format ssh git config --global tag.gpgSign true
- Set your SSH key for signing in Git with the following command, substituting
/PATH/TO/.SSH/KEY.PUBwith the path to the public key you'd like to use, e.g.
git config --global user.signingkey /PATH/TO/.SSH/KEY.PUB
Ensure you add your SSH key to your GitHub account as a Signing Key (as opposed to or in addition to as an Authentication Key).
Rebase on Git pull¶
git pull --rebase instead of
git pull when pulling in changes from GitHub to your local machine. This way your local changes will always be "on top of" the latest changes on GitHub, and you avoid merge commits (which are disallowed in this repo).
You can set this to be the default behavior:
git config --global pull.rebase true
main before submitting a PR¶
If you are working on your own branch, run these commands before submitting a PR:
git fetch origin
git rebase origin/main
Share this website and spread privacy knowledge
Copy this text to easily share Privacy Guides with your friends and family on any social network!