fix: cascade workflow — use PR-based merge for Gitea #10

Merged

jmiller merged 1 commits from fix/cascade-dev-gitea-api into main

2026-05-05 20:43:58 +00:00

Author	SHA1	Message	Date
Jonathan Miller	5d0040b886	fix: use PR create+merge for cascade (Gitea has no direct merge API) Repo Health / Access control (push) Successful in 1s Details Repo Health / Release configuration (push) Failing after 2s Details Repo Health / Scripts governance (push) Successful in 2s Details Repo Health / Repository health (push) Failing after 3s Details Joomla Extension CI / Release Readiness Check (pull_request) Successful in 3s Details Repo Health / Access control (pull_request) Successful in 1s Details Repo Health / Release configuration (pull_request) Failing after 3s Details Repo Health / Scripts governance (pull_request) Successful in 3s Details Repo Health / Repository health (pull_request) Failing after 3s Details PR Check / Validate PR (pull_request) Successful in 20s Details Joomla Extension CI / Lint & Validate (pull_request) Failing after 44s Details Joomla Extension CI / Tests (PHP 8.2) (pull_request) Has been skipped Details Joomla Extension CI / Tests (PHP 8.3) (pull_request) Has been skipped Details Gitea doesn't support POST /repos/{owner}/{repo}/merges. Rewrites the cascade workflow to: compare branches, create a PR (main → dev), then auto-merge if clean. On conflict the PR stays open for manual resolution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-05 15:43:36 -05:00