We could implement a more machine friendly way of specifying the lifecycle of a repo, e.g. in a root level lifecycle.json file, which could then be ingested to be used as input for badge creation.
The json could look like
{
"lifecycle": "experimental"
}
and then a badge could be made with a static URL like
We could implement a more machine friendly way of specifying the lifecycle of a repo, e.g. in a root level
lifecycle.json
file, which could then be ingested to be used as input for badge creation.The json could look like
and then a badge could be made with a static URL like
test repo https://github.com/RMI-PACTA/test-lifecycle/
⚠️ "raw" GitHub content is cached for 5 minutes, so a change would not be seen until 5 minutes after the commit