sunfloweracres/sunfloweracres-campaigns
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bump eec-campaigns to v0.1.7, scope sync to changed campaigns
Sync campaigns / sync (push) Successful in 18s
Details

Browse Source 
Only the campaign(s) whose files changed in this push get resolved and
diffed against listmonk now, instead of every campaign every time --
falls back to a full scan automatically if the before-commit can't be
determined. fetch-depth: 0 so that commit is always available to diff
against locally.
This commit is contained in:
Will Estes
2026-08-13 13:41:10 -04:00
parent 35cfd63945
commit c4de53f4bb
5 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -20,7 +20,7 @@ Alternatively, run the `Send campaign` workflow manually from Gitea Actions with
Repo secrets (Gitea Actions → Secrets) are already set: `CAMPAIGNS_LISTMONK_BASE_URL`, `CAMPAIGNS_LISTMONK_API_USER`, `CAMPAIGNS_LISTMONK_API_TOKEN`, `CAMPAIGNS_PREVIEW_EMAIL` (`hello@sunfloweracressoaps.com`, also a confirmed subscriber on `sunfloweracres-list` so test-sends have somewhere to go) — scoped to a dedicated `campaigns-sunfloweracres` listmonk API user (see `reground-infrastructure`'s `campaigns-sunfloweracres` Ansible role).
The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (currently `v0.1.6`). Bump that pin deliberately when a new tool version is ready, not automatically.
The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (currently `v0.1.7`). Bump that pin deliberately when a new tool version is ready, not automatically.
## Sending as hello@sunfloweracressoaps.com