MokoConsulting/Template-Joomla
Template
1
0
Fork 0
Code Issues Pull Requests Releases 3 Wiki Activity

feat(workflows): move dev-cascade into dedicated cascade-dev.yml #51

Merged
jmiller merged 1 commits from feat/cascade-dev-workflow into main 2026-07-05 19:39:56 +00:00
Conversation 0 Commits 1 Files Changed 2
+66 -19
jmiller commented 2026-07-05 19:36:34 +00:00
Owner
Copy Link
Copy Source

Moves the "recreate dev from main" function out of auto-release.yml Step 11 into its own workflow, and makes it actually work on protected branches.

What changed

  • cascade-dev.yml (new): on completion of "Universal: Build & Release" (+ manual workflow_dispatch), force-push main → dev. The automation identity is force-push allowlisted on dev via branch-protection.yml, so this works where the old delete+recreate could not (Gitea refuses to delete a protected branch). Force-push (not merge) means no version-file conflicts; running after the release means dev picks up the fully version-bumped + changelog-promoted main. Skips Template-* repos; concurrency-guarded.
  • auto-release.yml Step 11: drop the dev delete/recreate block; keep the rc cleanup.

Why

The old Step 11 tried DELETE /branches/dev then re-create — which silently failed once dev became a protected branch, leaving dev stale after each release. A dedicated force-push workflow is the reliable path now that the bot is force-push allowlisted (#334 / #54 / #49).

Refs #53.

https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i

Moves the "recreate dev from main" function out of `auto-release.yml` Step 11 into its own workflow, and makes it actually work on protected branches. ## What changed - **`cascade-dev.yml` (new):** on completion of "Universal: Build & Release" (+ manual `workflow_dispatch`), force-push `main` → `dev`. The automation identity is force-push allowlisted on `dev` via `branch-protection.yml`, so this works where the old delete+recreate could not (Gitea refuses to delete a protected branch). Force-push (not merge) means no version-file conflicts; running *after* the release means `dev` picks up the fully version-bumped + changelog-promoted `main`. Skips `Template-*` repos; concurrency-guarded. - **`auto-release.yml` Step 11:** drop the `dev` delete/recreate block; keep the rc cleanup. ## Why The old Step 11 tried `DELETE /branches/dev` then re-create — which silently failed once `dev` became a protected branch, leaving `dev` stale after each release. A dedicated force-push workflow is the reliable path now that the bot is force-push allowlisted (#334 / #54 / #49). Refs #53. https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i
jmiller added 1 commit 2026-07-05 19:36:34 +00:00
feat(workflows): move dev-cascade into dedicated cascade-dev.yml
Generic: Project CI / Lint & Validate (pull_request) Has been skipped
Details
Universal: PR Check / Branch Policy (pull_request) Failing after 2s
Details
Universal: PR Check / Validate PR (pull_request) Has been skipped
Details
Joomla: Metadata Validation / Validate Joomla Metadata (pull_request) Has been skipped
Details
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Generic: Repo Health / Access control (pull_request) Successful in 1s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 5s
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 1s
Details
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Details
Universal: Workflow Sync Trigger / Sync workflows to live repos (pull_request) Successful in 10s
Details
Generic: Project CI / Tests (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Details
Generic: Repo Health / Scripts governance (pull_request) Has been cancelled
Details
Generic: Repo Health / Repository health (pull_request) Has been cancelled
Details
Generic: Repo Health / Report: Scripts Governance (pull_request) Has been cancelled
Details
Generic: Repo Health / Report: Repository Health (pull_request) Has been cancelled
Details
c84fd09e18 
Moves the "recreate dev from main" function out of auto-release.yml Step 11
into its own workflow, and makes it actually work on protected branches.

- cascade-dev.yml: on release-workflow completion (+ manual dispatch),
  force-push main -> dev. The bot is force-push allowlisted on dev via
  branch-protection.yml, so this works where delete+recreate could not
  (Gitea refuses to delete a protected branch). Force-push (not merge) =>
  no version-file conflicts; running after the release => dev gets the
  fully version-bumped + changelog-promoted main. Skips Template-* repos;
  concurrency-guarded.
- auto-release.yml Step 11: drop the dev delete/recreate; keep rc cleanup.

Refs Template-Generic#53; enabled by the bot allowlist (#334/#54/#49).

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i
jmiller merged commit d93c69da9d into main 2026-07-05 19:39:56 +00:00
jmiller deleted branch feat/cascade-dev-workflow 2026-07-05 19:39:56 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Priority -
Type -
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/Template-Joomla#51
Delete Branch "feat/cascade-dev-workflow"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?