Skip to content

Keep local publish queue; rely on deploy-github-pages@asf for cross-repo races - #175

Merged
jamesfredley merged 1 commit into
mainfrom
drop-publish-concurrency-queue
Sep 3, 2026
Merged

Keep local publish queue; rely on deploy-github-pages@asf for cross-repo races#175
jamesfredley merged 1 commit into
mainfrom
drop-publish-concurrency-queue

Conversation

@jamesfredley

Copy link
Copy Markdown
Contributor

Summary

  • This repo already publishes with apache/grails-github-actions/deploy-github-pages@asf. After apache/grails-github-actions#110, that action retries genuine non-fast-forward races on apache/grails-website (rebase the unpublished commit, never force-push).
  • Unlike grails-core docs jobs, every Forge UI run purges and rewrites the same start/ path. The repository-local publish-grails-forge-ui concurrency group is kept so two main publishes cannot overwrite /start out of order. GitHub concurrency groups are repo-scoped and cannot replace Update gradle action version to an approved ASF version #110 for grails-core / grails-static-website.
  • Cross-repo push still requires GH_TOKEN: ${{ secrets.GRAILS_GHTOKEN }}. The default GITHUB_TOKEN cannot write apache/grails-website. Job permissions: contents: write is unchanged as the action's same-repo fallback. GRAILS_GHTOKEN is not a repo-level secret visible here; it is the same org/environment PAT grails-core and grails-static-website already use, and the last Publish run on main succeeded.

Test plan

  • Confirm .github/workflows/publish.yml still calls deploy-github-pages@asf with TARGET_REPOSITORY: apache/grails-website, LAST_SNAPSHOT_FOLDER: start, and GRAILS_GHTOKEN.
  • Confirm the publish-grails-forge-ui concurrency group remains (cancel-in-progress: false).
  • After merge, run Publish via workflow_dispatch and verify https://grails.apache.org/start/ updates.

Every publish rewrites /start, so same-repo serialization stays. Cross-repo
races on grails-website are handled by deploy-github-pages@asf after
apache/grails-github-actions#110.
Assisted-by: Cursor:Grok-4.6
CopilotAI lite review requested due to automatic review settings September 3, 2026 00:49

CopilotAI 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.

🟢 Approval recommended

The change is limited to comment updates in the workflow file and does not alter execution logic, permissions, or publish behavior.

Pull request overview

Updates the GitHub Actions publish workflow commentary to clarify why this repository keeps a local concurrency queue for /start publishes while relying on apache/grails-github-actions/deploy-github-pages@asf to handle cross-repo non-fast-forward races when pushing to apache/grails-website.

Changes:

  • Rewords and expands the inline workflow comments explaining the purpose/scope of the publish-grails-forge-ui concurrency group.
  • Documents that cross-repo publish races are handled by deploy-github-pages@asf (per apache/grails-github-actions#110) and that GitHub concurrency groups are repo-scoped.
File summaries
FileDescription
.github/workflows/publish.ymlClarifies concurrency intent and cross-repo race handling via updated comments (no functional workflow changes).
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

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

@jamesfredley
jamesfredley merged commit 7279749 into mainSep 3, 2026
2 checks passed
@jamesfredley
jamesfredley deleted the drop-publish-concurrency-queue branch September 3, 2026 00:50
Sign up for freeto 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

@jamesfredley