Skip to content

fix(ci): Blog → README Sync — push to dev instead of main #270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mpaulosky merged 1 commit into from
May 8, 2026
Merged

fix(ci): Blog → README Sync — push to dev instead of main #270

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/blog-readme-sync.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,5 +78,5 @@ jobs:
git diff --quiet README.md || (
git add README.md &&
git commit -m "docs: sync Dev Blog section from docs/blog/index.md [skip ci]" &&
git push
git push origin HEAD:dev
)
Comment on lines 78 to 82
12 changes: 12 additions & 0 deletions .squad/agents/boromir/history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,18 @@

## Learnings

### 2026-05-XX — Issue #269: Blog → README Sync workflow branch protection fix

**Problem:** `blog-readme-sync.yml` pushed directly to `main` after updating `README.md`, which is blocked by branch protection rules (direct pushes forbidden, "Build Solution" check required).

**Fix (Option C):** Changed `git push` to `git push origin HEAD:dev` in the "Commit updated README" step. The workflow still triggers on `push: branches: [main]` (reading `docs/blog/index.md` from main), but the README update is pushed to `dev` — the normal development branch — and flows through the standard dev→main release cycle.

**Key insight:** The `permissions: contents: write` block was already present. No new secrets or PAT bypass needed. One-line change.

**Decision:** Captured in `.squad/decisions/inbox/boromir-269-readme-sync-target.md`.

---

### 2026-05-08 — Issue #249: AppHost Mongo Clear Hardening

**What was done:**
Expand Down
Loading