Skip to content

AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).

chore(ci): tidy release workflow comments (#349)

Rufusa619a997a39a
diff --git a/.github/workflows/release-images.yml b/.github/workflows/release-images.yml
index c0203e55..412e6bcb 100644
--- a/.github/workflows/release-images.yml
+++ b/.github/workflows/release-images.yml
@@ -13,10 +13,9 @@
# on main that CI has passed. The two images are separate matrix jobs, so a
# release is not atomic — if one job fails, the other's tags still exist.
#
-# The job is guarded to this repository: the saas fork syncs with
-# `git merge upstream/main` and would otherwise run this on every push to its
-# own main, and a third-party fork would fail with a 403 pushing to the
-# hardcoded ghcr.io/sentelabsai/* names. A fork that wants its own images
+# The job is guarded to this repository: a fork would otherwise run this on
+# every push to its own main and fail with a 403 pushing to the hardcoded
+# ghcr.io/sentelabsai/* names. A fork that wants its own images
# changes the guard and the image names.
#
# Version tags normally come from merging the release PR that
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml
index 5f840d74..590dd876 100644
--- a/.github/workflows/release-please.yml
+++ b/.github/workflows/release-please.yml
@@ -33,8 +33,8 @@
# the release tag would publish no images. Use a fine-grained token scoped to
# this repository with Contents and Pull requests read/write.
#
-# Guarded to this repository for the same reason as release-images.yml: the
-# saas fork merges upstream/main and must not open release PRs of its own.
+# Guarded to this repository, as release-images.yml is, so a fork never opens
+# release PRs of its own.
name: Release please
on: