Create playbook from antora-playbook.yml + a patch file #698
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.
Why
We maintain a bunch of playbooks locally, or for other environments, which eventually get out of sync with our main branch.
This means e.g. we forget to add new branches or extensions to Staging, or forget to update our ui-bundle locally etc.
When we have a local playbook that works, it's still a hassle to manually create the remote playbook for previewing.
Use Cases
See example
patch.yml
in this PR.Operators like
$filter
,$prune
,$local
will cut down to certain repos, limit to a manageable number of branches, and turn the remote refs into local ones if you have them checked out.This example again uses
$prune
to limit to the most recent X branches.We can also
$override
individual repos, to add particular branches/start_paths etc. (e.g. for the devex private preview)