[twk3]

Stops main's docs deploy from force-pushing over gh-pages (ENG-1736).

gh-pages is about to receive pushes from three places:

• main's docs deploy, to docs/;
• release-0.8's docs deploy, to 0.8/docs (docs: publish the 0.8 docs under 0.8/docs, pinned to chart 0.8.1 [ENG-1736] #62);
• chart-releaser, to index.yaml.

JamesIves/github-pages-deploy-action force-pushes by default. A deploy that checks out gh-pages, then pushes after one of the others, drops the other's commit: 0.8/docs reverts, or a new chart version disappears from index.yaml.

Changes

• force: false: the action rebases its commit onto the current gh-pages instead.
• A concurrency group per branch, sync-docs-${{ github.ref }}: keeps main's own deploys in order. A queued deploy can be dropped, because the next one carries every earlier change.

There's deliberately no group shared with release-0.8. GitHub keeps one pending run per group and cancels the older one, which would silently drop the other branch's deploy.

#62 makes the same change on release-0.8. Merge this one before or with it.

Testing

• The workflow parses, with force: false and the concurrency group in place.
• The deploy itself runs on the next push to main.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UhM4wHR2xPP8bbrkXGaqUD

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[baz-reviewer]

Baz Summary

Update the sync-docs workflow to rebase documentation deployments onto gh-pages instead of force-pushing, preserving concurrent release and chart updates. Serialize main deployments with a branch-specific concurrency group while allowing other branches to publish independently.

Latest Contributors(1)

User	Commit	Date
dj@currents.dev	ci: rebase the docs de...	October 14, 2026

  _{Activate to get a short verdict whether this PR is good to go or not}

  _{Activate Skill Maintainer to keep your skills up to date}

  _{This PR would have been improved with Baz Planner - Try it now}