diff options
| author | PandaNinjas <admin@malwarefight.gq> | 2023-02-19 02:05:35 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-19 02:05:35 +0000 |
| commit | 018e644141c27ef369cd94a7385fa8a782ab0a8d (patch) | |
| tree | f96e2ddaf426da6e5e2d30271ec0b4bb4ef65c94 | |
| parent | 5bdb58d557a13abaaf8241dab9d1253f2c19843e (diff) | |
| download | NoSession-018e644141c27ef369cd94a7385fa8a782ab0a8d.tar.gz NoSession-018e644141c27ef369cd94a7385fa8a782ab0a8d.tar.bz2 NoSession-018e644141c27ef369cd94a7385fa8a782ab0a8d.zip | |
Remove misinformation
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -24,4 +24,4 @@ See [SECURITY.md](SECURITY.md) - Does not break existing token login methods
## Contributing
-All pushes to the main branch *must* be signed with a GPG key. See https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key and https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account for how
+All pushes to the main branch *must* be signed with a cryptographic key. See https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key and https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account for how
|