Benjamin_Loison/Verified_repositories
1
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity

Precise in README.md alternative method when having contributed to the repository of someone else to prove authenticity of own commits

Browse Source
This commit is contained in:
Benjamin Loison 2023-02-01 17:47:45 +01:00
parent b6b5454bc6
commit 38e27c698c
Signed by: Benjamin_Loison
SSH Key Fingerprint: SHA256:BtnEgYTlHdOg1u+RmYcDE0mnfz1rhv5dSbQ2gyxW8B8
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -17,7 +17,7 @@ Default template:
// Mandatory: git state hash verified. // Mandatory: git state hash verified.
"commit": "0123456789abcdef0123456789abcdef01234567", "commit": "0123456789abcdef0123456789abcdef01234567",
// Optional (default: "VERIFIED"): xor of following flags (written as `FLAG_0 | FLAG_1 | ... | FLAG_N`): // 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` // - `CLOSED_SOURCE_DEPENDENCY`
// - `UNVERIFIED_INITIAL_COMMIT` // - `UNVERIFIED_INITIAL_COMMIT`
"status": "VERIFIED", "status": "VERIFIED",