Move docs workflows to elastic/docs-actions#1397
Conversation
Moves docs CI/CD from elastic/docs-builder to elastic/docs-actions. Part of elastic/docs-eng-team#474
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe GitHub Actions workflow configuration migrates from ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Moves our docs CI/CD workflow logic from
elastic/docs-buildertoelastic/docs-actions.elastic/docs-builderhas grown in scope;elastic/docs-actionslets thedocs team push updates to the
@v1tag independently without coupling tothe broader builder tooling.
The new setup follows GitHub's recommended two-phase workflow approach:
all required checks on pull requests now run with read-only access only.
Preview deployments and PR comments happen in a separate phase triggered
after the required check completes.
Replaces
preview-build.ymlanddocs-cleanup.ymlwith three new workflowfiles:
docs-build.yml,docs-deploy.yml, anddocs-preview-cleanup.yml.Preview deployments for forks:
Preview deployments are not available for fork PRs by default. If you are an
Elastic employee working from a fork, previews will work once your Elastic
GitHub organization membership is set to Public:
Go to https://github.com/orgs/elastic/people and find your name
Open the visibility dropdown next to your name and select Public
Or: GitHub profile -> Organizations -> Elastic logo -> set visibility
to Public.
Contributors outside Elastic will still get build validation feedback on
their PRs -- only preview deployments are skipped.
Post-merge
docs-buildinstead ofpreview-build(if applicable)cc @elastic/ingest-docs