You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potentially use github action with script
Mkdocs will auto create the nav depending on the file structures in the repos. Does this suit our use case ?
Potentially a plugin could help
The text was updated successfully, but these errors were encountered:
Should this be the responsibility of the kuadrant-operator repo. Would it be possible to set up a web hook in the repo that contains the Mkdocs configuration that reacts to new docs being added here. This way any repo that the docs repo pulls in can be watched from one location.
It seem wrong for this repo to be concerned with handling the automation of a different repo. It does not add value to the operator. I understand it would add value to the docs and therefore the user, but not the operator. It is automation that would need to be maintained.
WHAT
Potentially use github action with script
Mkdocs will auto create the nav depending on the file structures in the repos. Does this suit our use case ?
Potentially a plugin could help
The text was updated successfully, but these errors were encountered: