ci: disable auto-trigger on doxygen-pages + perf workflows #21
Reference in New Issue
Block a user
No description provided.
Delete Branch "ci/disable-auto-pages-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?
Restrict both workflows to workflow_dispatch only until the pages-branch push issue from the v0.10.0 merge is debugged. No code or doc changes.
Both workflows used `push: branches: [main]` and have been firing on every merge to main since v0.10.0 landed. Recent runs failed: * `doxygen-pages.yml` runs #492/#493/#494 — failed (pages branch went into an inconsistent state during the cleanup sequence; the workflow's HTTPS push couldn't recover, even though manual SSH push from a developer machine could). * `perf-compile-time.yml` never ran a clean baseline because the same upstream CI-container issue blocks it. While we work through the root cause, both workflows are restricted to `workflow_dispatch` (manual only). Effect: * pages-branch stays at its last known-good content; merges to main no longer trigger a (currently-failing) republish attempt * no false-red CI badges on PRs / commits * either workflow can still be fired manually via the Gitea Actions UI when needed Re-enable trick: each file has its old `push:` block commented out; uncomment when the underlying CI push issue is fixed. `doc-build.yaml` (Doxygen warning-stats, `continue-on-error: true`) is unaffected — it does not push anywhere and is intentionally informational. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>