Skip to content

⭐️⭐️⭐️ Open-source, self-hosted alternative to Linear and Plane. Project management and issue tracking where teams and AI agents work side by side to plan and ship products.

ci: move the release branch push into the release workflow (#43)

Croffb8559da9a871
diff --git a/.github/workflows/release-branch.yml b/.github/workflows/release-branch.yml
deleted file mode 100644
index 7a82e5e8..00000000
--- a/.github/workflows/release-branch.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-name: Release branch
-
-# Moves the `release` branch to the commit of every published GitHub Release, so
-# a deploy target that follows a branch (Coolify) runs released versions only.
-# The branch is a mirror: this workflow is the only writer, which keeps the push
-# a fast-forward. It is created on the first published release.
-on:
- release:
- types: [published]
-
-# Needed to push the branch with GITHUB_TOKEN. Do not protect `release` with a
-# rule that requires a pull request: GITHUB_TOKEN cannot push through it.
-permissions:
- contents: write
-
-concurrency:
- group: release-branch
- cancel-in-progress: false
-
-jobs:
- sync:
- name: Move the release branch
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
- with:
- ref: ${{ github.event.release.tag_name }}
-
- - run: git push origin HEAD:release
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 6b9ed797..0f7efec3 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -7,7 +7,7 @@ on:
push:
branches: [main]
-# Needed to open the release PR and create tags/releases with GITHUB_TOKEN.
+# Needed to open the release PR, create tags/releases, and push `release`.
permissions:
contents: write
pull-requests: write
@@ -22,6 +22,27 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@v5
+ id: release
with:
config-file: release-please-config.json
manifest-file: .release-please-manifest.json
+
+ # Move the `release` branch to the released commit, so a deploy target
+ # that follows a branch (Coolify) runs released versions only. The branch
+ # is a mirror: this job is the only writer, which keeps the push a
+ # fast-forward. It is created on the first published release.
+ #
+ # This runs here rather than in a workflow triggered by `release:
+ # published`, because that event is raised by GITHUB_TOKEN and
+ # GITHUB_TOKEN-triggered events do not start workflow runs.
+ #
+ # `release_created` is set only when a release was cut; it has no `false`
+ # value, so an unset output makes the condition skip the steps.
+ - uses: actions/checkout@v7
+ if: ${{ steps.release.outputs.release_created }}
+ with:
+ ref: ${{ steps.release.outputs.tag_name }}
+
+ - name: Move the release branch
+ if: ${{ steps.release.outputs.release_created }}
+ run: git push origin HEAD:release
diff --git a/AGENTS.md b/AGENTS.md
index b490f99c..4ad94ff9 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -182,10 +182,10 @@ keeps its `autorelease: pending` label, and every later run stops at
name makes both sides resolve to no component. Tags stay `vX.Y.Z` — that is
`include-component-in-tag: false`, a separate setting.
-Publishing a release moves the `release` branch to the released commit
-(`release-branch.yml`), which is what the deploy target follows. `main` stays the
-only branch anyone works in; `release` is a mirror with a single writer, so it
-never needs a merge back. It appears with the first published release.
+Cutting a release also moves the `release` branch to the released commit, which
+is what the deploy target follows. `main` stays the only branch anyone works in;
+`release` is a mirror with a single writer, so it never needs a merge back. It
+appears with the first published release.
**Agents do not commit.** Do the work, then write the proposed commit message in
chat as a Conventional Commit (`type(scope): summary`) for the user to run. Do
diff --git a/README.md b/README.md
index 2e921c9e..41ae8b83 100644
--- a/README.md
+++ b/README.md
@@ -114,14 +114,24 @@ Alternatively, run the same gate CI uses — the suite against a throwaway Postg
container built from the production image:
```bash
-docker compose -f docker-compose.test.yml up --build \
- --abort-on-container-exit --exit-code-from api-test
+docker compose -f docker-compose.test.yml build
+docker compose -f docker-compose.test.yml run --rm api-test
```
+`run` starts the dependencies, runs the suite, and exits with its code.
+
### Deploy on Coolify
-Point a Docker Compose resource at `docker-compose.coolify.yml`. Coolify supplies the
-secrets and domains through its own generated variables; nothing else to configure.
+Create a **Git Based** resource pointing at the public repository, with **Docker Compose**
+as the build pack and `docker-compose.coolify.yml` as the compose file. Set the branch to
+`release` and the commit SHA to `HEAD`.
+
+`release` is a mirror branch that the release workflow moves to each published release, so
+the deploy runs released versions only. It appears with the first published release; until
+then there is nothing to deploy from.
+
+Coolify supplies the secrets and domains through its own generated variables; nothing else
+to configure.
### Self-hosting (production)