-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Automate testing of updatecli manifest example #188
Comments
+1 with the venom proposal. Proposal: switch documentation to be built through https://antora.org/ .
|
Proposal: switch documentation to be built through https://antora.org/ . I am not familiar with Antora so I am interested for a bootstrap discussion to see if it would help us |
I'm planning to work on it after updatecli/updatecli#465. I was thinking using my forkgs of website + updatecli to provide a PoC. Anyone interested in welcome to try as well of course! |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Summary
The current doc contains many outdated examples.
We could move all examples to dedicated yaml files and then similar to updatecli/updatecli#419, using venom to validate that example are not returning warnings.
Basic example
Include a basic example or links here.
Motivation
Better catch outdated updatecli examples
The text was updated successfully, but these errors were encountered: