summaryrefslogtreecommitdiff
path: root/.github/workflows/docs.yml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* cicd: Use minimum_zig_version instead of masterGravatar Jimmi Holst Christensen2025-11-261-15/+12
|
* chore: bump actions/checkout from 4 to 5Gravatar Jimmi Holst Christensen2025-08-161-1/+1
|
* chore: Update setup-zig to v2Gravatar Jimmi Holst Christensen2025-05-071-1/+1
|
* chore: bump deploy-pages action versionGravatar Jora Troosh2025-02-241-1/+1
|
* chore: Update upload-pages-artifactGravatar Jimmi Holst Christensen2025-02-211-1/+1
|
* chore: Update upload-artifactGravatar Jimmi Holst Christensen2025-02-211-1/+1
|
* fix: Cicd use `with: master` as `latest` is the defaultGravatar Jimmi Holst Christensen2024-09-131-0/+2
|
* chore: Use mlugg/setup-zig instead of goto-bus-stop/setup-zigGravatar Jimmi Holst Christensen2024-09-131-3/+1
|
* cicd: Only depend on major versionsGravatar Jimmi Holst Christensen2024-02-021-1/+1
|
* Add autodoc websiteGravatar Abhinav Gupta2024-01-021-0/+47
This adds a `zig build docs` step that builds the documentation website and writes it to zig-out/docs. It further includes a GitHub Workflow that publishes this website to GitHub Pages. The GitHub Workflow is divided into two jobs: - build: builds the documentation and uploads it - publish: downloads the documentation and publishes it These are separate jobs to minimize permissions available to the build job. This workflow runs on two events: - after every push to master - `workflow_dispatch`: this allows manually running the workflow from its *Actions* page if something went wrong --- **Important pre-merge steps:** If this PR is accepted, the following steps should be taken before merging the PR: 1. Go to **Settings** for the repository 2. Select **Pages** on the left under *Code and automation* 3. Under *Build and deployment* set **Source** to **GitHub Actions** 4. Merge the PR. If the steps are missed, the PR will merge just fine, but the docs job will fail immediately on merge. This can be remedied by following steps 1-3 above, and either adding a new commit on master, or manually firing the workflow from the Actions > API Reference page.