Skip to content

Pass SYNC_TOKEN to the studio frontend build - #129

Draft
berfinyuksel wants to merge 1 commit into
5.2from
ci/frontend-build-sync-token
Draft

berfinyuksel wants to merge 1 commit into
5.2from
ci/frontend-build-sync-token

Conversation

@berfinyuksel

Copy link
Copy Markdown
Contributor

Part of pimcore/DevOps-Tasks#65. The studio frontend build pushes its automatic commits as pimcore-deployments and only on pushes to version branches; PR runs upload the build as an artifact instead (pimcore/workflows-collection-public#168). The push run no longer cancels an in-progress run; the head-commit check in the reusable prevents a commit loop.

Until #168 is merged the "Studio Frontend Build" check fails at startup with "secret SYNC_TOKEN is not defined in the referenced workflow". That is expected; the check gets re-run after the merge, before this PR is marked ready.

Build commits are pushed as pimcore-deployments and only on version
branches; PR runs upload the build as an artifact instead
(pimcore/workflows-collection-public#168, DevOps-Tasks#65). The push run
no longer cancels an in-progress run, the head-commit check in the
reusable prevents a commit loop.
@berfinyuksel berfinyuksel added the Skip Milestone Check Exempts this PR from the mandatory milestone requirement label Oct 6, 2026
@sonarqubecloud

sonarqubecloud Bot commented Oct 6, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip Milestone Check Exempts this PR from the mandatory milestone requirement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant