Skip to content

ci: split the docs workflow into build, commit and deploy jobs - #1217

Open
B4nan wants to merge 1 commit into
masterfrom
ci/split-docs-jobs
Open

B4nan wants to merge 1 commit into
masterfrom
ci/split-docs-jobs

Conversation

@B4nan

@B4nan B4nan commented Nov 17, 2026

Copy link
Copy Markdown
Member

The docs workflow ran the whole docs toolchain (pnpm install, the theme update, the Docusaurus build) in the same job that holds the service account token. Now the build job only gets a read-only GITHUB_TOKEN and hands the changed files over as an artifact, and a separate job that runs no toolchain does the signed commit. The Pages deploy and CloudFront invalidation get their own job too.

The workflow only runs from master, so this can't be exercised before merge. actionlint is clean.

The docs toolchain now runs in a job with a read-only token. The signed commit, the Pages deploy and the CloudFront invalidation run in separate jobs that do not install or build anything.
@B4nan B4nan added t-tooling Issues with this label are in the ownership of the tooling team. adhoc Ad-hoc unplanned task added during the sprint. labels Nov 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

⚠️ There are broken links in the documentation.

See more at https://github.com/apify/apify-client-js/actions/runs/44062271701#summary-133966910179

@B4nan
B4nan requested review from barjin and vdusek November 18, 2026 07:31

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant