Include assembling the downstream doc in the default doc pipeline #35479
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will backport it to 3.2 once CI is green and will ping you when it's done. |
|
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
|
Thanks @gsmet 💯 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will include the downstream doc as part of the default pipeline.
So if you build the documentation as you used to (to get the transformed output), you will end up with the downstream doc in
docs/target/downstream-tree.Then you could automatically sync the result every day from the 3.2 branch given we only push doc fixes to the 3.2 branch. I'm not familiar with your GitLab setup but you should be able to set up a workflow doing that. I can help on the Quarkus specific side if you have someone familiar with GitLab around.