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
{{ message }}
Repository navigation
Commit df2d47a
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/workflows/README-update-antora-ui-bundle.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,17 @@ rather than there being one canonical file on the default branch. Branches that
43
43
Antora adoption have no such file at all; those are reported as `no-playbook` rather than an
44
44
error.
45
45
46
+
## The `docs-build` playbook
47
+
48
+
Every Antora project also keeps a repo-wide `docs-build` branch whose root
49
+
`antora-playbook.yml`pins the same UI bundle URL. It is one branch per repository (not one
50
+
per maintained branch), so `setup` adds one extra matrix entry per repository —
51
+
`branch: docs-build`, `playbook_path: antora-playbook.yml` — and the `update` job handles it
52
+
through the same PR flow, statuses, auto-merge and notification as the per-branch playbooks.
53
+
The PR head is `antora-ui-bundle-update/docs-build-<tag>`. Either `.yml` or `.yaml` is accepted (`.yml` first), for both kinds of playbook. A repository with no
54
+
playbook on `docs-build` is reported as `no-playbook`. The `-internal` exclusion
55
+
does not apply.
56
+
46
57
### What is out of scope
47
58
48
59
- **`-internal` branches are skipped**, for the same reason
0 commit comments