Commit Graph

6 Commits

Author SHA1 Message Date
f04e95cfae
Add a description to VERIFIED_ONLY_OWN_COMMITS status flag in README.md template
Note that here I talk about commits and not git state. I don't even know
if talking about global commits diff like a git state diff make sense as
commits happening between the first and last known to date verifier can contain commits from other users.
2023-02-01 01:48:20 +01:00
7d9b6e3924
Add VERIFIED_ONLY_OWN_COMMITS status flag in README.md template 2023-02-01 01:35:41 +01:00
8f8056ded4
Add default template to README.md introducing status and comment optional fields 2023-02-01 01:20:48 +01:00
66b7e574fb
Precise the notion of repository state in README.md 2023-02-01 00:44:53 +01:00
32263625f5
Precise the current trust level target in README.md
I thought about adding the following convention:

> Current convention is such that if a folder exists but just contains `.gitkeep`, it means that everything that could fall into this folder and isn't existing is considered as verified.

This would be useful for personal git users, but it's an edge case and
would anyway need to precise an overwhole git user gits hash to confirm
a statement at a given gits state.
So let's keep the same convention for every git.
2023-02-01 00:38:24 +01:00
fd7ad7a93d
Add README.md 2023-01-31 23:43:23 +01:00