Skip to content

fix(site): respect protected version sync branch - #3

Merged
foobarto merged 1 commit into
mainfrom
codex/protected-version-sync
Aug 13, 2026
Merged

fix(site): respect protected version sync branch#3
foobarto merged 1 commit into
mainfrom
codex/protected-version-sync

Conversation

@foobarto

Copy link
Copy Markdown
Owner

Summary\n- update the weekly version sync to use a dedicated automation PR instead of pushing directly to protected main\n- squash-merge that PR, then explicitly request the Pages build\n- retain idempotency when an automation PR is already open\n\n## Verification\n- make test\n- make lint\n- node --check docs/assets/site.js\n- YAML parse and staged Gitleaks scan

Copilot AI lite review requested due to automatic review settings August 13, 2026 20:01
@foobarto
foobarto merged commit 342f6b4 into main Aug 13, 2026
1 check passed
@foobarto
foobarto deleted the codex/protected-version-sync branch August 13, 2026 20:01

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the scheduled website version sync workflow to avoid pushing directly to protected main by instead creating an automation pull request, squash-merging it, and then explicitly triggering a GitHub Pages build.

Changes:

  • Add pull-requests: write permission and switch the workflow from direct git push ...:main to gh pr create + gh pr merge.
  • Add idempotency logic to detect an already-open version-sync PR and skip creating a duplicate.
  • Gate the Pages build request on whether the automation PR was actually merged.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
test/site_test.py Updates workflow-content assertions to match the new PR-based sync approach and required permissions.
.github/workflows/sync-site-version.yml Reworks the version sync job to create/merge an automation PR and then request a Pages build, compatible with protected branches.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +59 to +63
branch="automation/sync-site-version-${VERSION}"
existing_pr="$(gh pr list --base main --head "$branch" --state open --json number --jq '.[0].number')"
if [[ -n "$existing_pr" ]]; then
printf 'merged=false\n' >> "$GITHUB_OUTPUT"
printf 'An open version-sync PR already exists: #%s\n' "$existing_pr"
git commit -m "docs(site): sync version to ${VERSION}"
git push origin HEAD:main
git push --set-upstream origin "$branch"
pr_url="$(gh pr create --base main --head "$branch" --title "docs(site): sync version to ${VERSION}" --body "Automated website version update from \`VERSION\`.")"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants