Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: Build and Release

on:
push:
# Only trigger the heavy multi-platform build on version tag pushes (e.g. v1.9.1)
# Only trigger the heavy multi-platform build on version tag pushes (e.g. v1.9.8)
tags:
- 'v*'
# Allow manual dispatch for ad-hoc builds from the UI
Expand Down
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This document explains how our GitHub Actions are gated and how to trigger heavi

### CI design principles
- Lightweight checks (unit tests, linters) run on `push` / `pull_request` for `main` and `develop` branches.
- Heavy tasks (cross-platform builds, Docker image builds & push, release packaging) only run on tag pushes (e.g. `v1.9.1`) or when explicitly requested.
- Heavy tasks (cross-platform builds, Docker image builds & push, release packaging) only run on tag pushes (e.g. `v1.9.8`) or when explicitly requested.

This reduces wasted CI minutes and avoids building/publishing artifacts for every code merge.

Expand All @@ -13,8 +13,8 @@ There are multiple intentional ways to trigger full/heavy workflows:

- Push a semantic version tag (recommended for releases):
```bash
git tag v1.9.1
git push origin v1.9.1
git tag v1.9.8
git push origin v1.9.8
```
Tag pushes trigger the `build.yml` / `release.yml` flows which do cross-platform builds and create the Release.

Expand Down
Loading