ci(docs): publish on release and stop fork PRs failing on comment#850
Merged
michalharakal merged 1 commit intoJul 21, 2026
Merged
Conversation
Two documentation-workflow fixes: docs.yml: deploy the Antora site to GitHub Pages on `release: published` instead of on every push to develop, so the live site tracks the last released version. `build-docs` still runs on PRs/pushes for validation. The release event is immune to the `paths:` filter and checks out the released commit, where generateDocs/dokkaGenerate run live, so no generated pages need to be committed. documentation.yml: the "Create PR comment with preview link" step failed on fork PRs because such PRs get a read-only GITHUB_TOKEN regardless of the workflow's permissions block. Guard the step to same-repo PRs and mark it continue-on-error so a missing comment never fails the run.
|
📖 Documentation Preview The documentation has been built successfully for this PR. Generated Files:
Artifacts:
This comment will be updated automatically when the PR is updated. |
MacOS
approved these changes
Jul 21, 2026
This was referenced Jul 21, 2026
MacOS
pushed a commit
to MacOS/SKaiNET
that referenced
this pull request
Jul 22, 2026
…akes The single build-job ran `assemble allTests` in one ubuntu-latest job. On a 7 GB runner the combined peak memory (Gradle JVM + Kotlin daemon + per-target test forks + Node for JS/Wasm + native toolchain, all at once) intermittently exceeded physical RAM. The runner was OOM-killed and GitHub reported "The operation was canceled" after ~15 min with no BUILD FAILED — the flaky ~20-minute red builds (seen on PRs SKaiNET-developers#850, SKaiNET-developers#852). Changes: - Split the test run into a matrix of three legs (jvm / js-wasm / native), each running one target family so no single job holds the whole footprint. Legs run in parallel, so wall-clock is the slowest leg instead of the sum. - Run `assemble` as its own memory-light job, preserving the build/package guarantee for all targets. - Add Gradle dependency/wrapper caching to each job (same pattern as docs.yml) so parallel legs don't cold-download the dependency graph. - Capture the memory snapshot on `cancelled()` as well as `failure()` — an OOM-killed runner reports cancelled, not failed, so the existing diagnostic never fired on the runs that needed it. - Keep an aggregate `build-job` gate with the same name so the existing required status check keeps working without re-pointing branch protection. No production code changed; allTests passes locally.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Two documentation-workflow fixes.
docs.yml— publish docs on releaserelease: publishedinstead of on every push todevelop, so the live site tracks the last released version.build-docsstill runs on PRs/pushes for validation; only the deploy trigger moved.releaseevent is immune to thepaths:filter and checks out the released commit, wheregenerateDocs/dokkaGeneraterun live against the working tree — so no generated pages need to be committed. Single-version for now.documentation.yml— stop fork PRs failing on the preview commentGITHUB_TOKENregardless of the workflow'spermissions:block.github.event.pull_request.head.repo.full_name == github.repository) and mark itcontinue-on-errorso a missing comment never fails the run.Why
developpush.Scope / follow-up
docs/antora.yml(version: ~unchanged).Testing notes
github-scriptSHA).build-docscontinues to run on this PR.