From 38e27c698c8002c3b6de39853fb28180fa6ab5bb Mon Sep 17 00:00:00 2001 From: Benjamin Loison Date: Wed, 1 Feb 2023 17:47:45 +0100 Subject: [PATCH] Precise in `README.md` alternative method when having contributed to the repository of someone else to prove authenticity of own commits --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 31f9d89..2dda330 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ Default template: // Mandatory: git state hash verified. "commit": "0123456789abcdef0123456789abcdef01234567", // Optional (default: "VERIFIED"): xor of following flags (written as `FLAG_0 | FLAG_1 | ... | FLAG_N`): - // - `VERIFIED_ONLY_OWN_COMMITS`: means that the whole git state wasn't verified but the verifier commits were verified (note that using this flag for repositories that aren't managed by the verifier requires verifier commits to be signed and to precise the fingerprint of his public key in this `README.md` for instance) + // - `VERIFIED_ONLY_OWN_COMMITS`: means that the whole git state wasn't verified but the verifier commits were verified (note that using this flag for repositories that aren't managed by the verifier requires verifier commits to be signed and to precise the fingerprint of his public key in this `README.md` for instance) otherwise the commit hashes have to be precised in a way // - `CLOSED_SOURCE_DEPENDENCY` // - `UNVERIFIED_INITIAL_COMMIT` "status": "VERIFIED",