Adding CLI generated documentation
what's the intention? run and commit each cli change?
Yes, that's the idea, to have this CLI documentation available in the main repository.
would it make more sense to run and commit into skupper-docs? (and use versioning there for each minor release)
I think this is also a very good idea that we could implement additionally.
@nluaces @pwright I like the idea of having this being generated automatically, maybe on each PR merged or as a scheduled workflow in the CI. Can we get these markdown files incorporated into the skupper-docs somehow?
Can we get these markdown files incorporated into the skupper-docs somehow?
should we add the changes per release only in the skupper-docs, like @pwright suggested?
I would probably add them directly to skupper-website repo, based on release tag