Open fabiand opened 4 months ago
[fabiand@toolbox common-instancetypes (main)]$ git grep "Has GPUs"
README.md:*Has GPUs* | | | | ✓ | |
README.md:- *Has GPUs* - Has GPUs predefined.
[fabiand@toolbox common-instancetypes (main)]$
The README is partially auto generated, partially manually maintained.
See https://github.com/kubevirt/common-instancetypes/blob/main/scripts/readme.sh
Does this meet your requirements?
@0xFelix did you know about https://github.com/fabiand/instanceTypes/blob/main/hacks/docs.py (rendered: https://github.com/fabiand/instanceTypes/blob/main/README.md) ?
It's carefulyl written (tho not beautiful), because it addresses the following:
Does this meet your requirements?
because of the above i'd say carefully no.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
What happened: Could it be that the READ is manually maintainted instead of auto generated?
What you expected to happen: To have README.md to be auto generated
How to reproduce it (as minimally and precisely as possible): Always
Additional context: https://github.com/fabiand/instanceTypes/blob/main/hacks/docs.py is auto generating a readme based on the metadata/yamls.
Environment:
virtctl version
): N/Akubectl version
): N/Auname -a
): N/A