Precise in README.md
alternative method when having contributed to the repository of someone else to prove authenticity of own commits
This commit is contained in:
parent
b6b5454bc6
commit
38e27c698c
@ -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",
|
||||
|
Loading…
Reference in New Issue
Block a user