Skip to content

ci: allow manual workflow_dispatch trigger#197

Closed
DeepDiver1975 wants to merge 1 commit into
masterfrom
ci/add-workflow-dispatch
Closed

ci: allow manual workflow_dispatch trigger#197
DeepDiver1975 wants to merge 1 commit into
masterfrom
ci/add-workflow-dispatch

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member

What

Add a workflow_dispatch trigger to the CI workflow.

Why

CI consumes owncloud/reusable-workflows/.github/workflows/acceptance.yml@main.
When a fix lands upstream in that reusable workflow, re-running an existing
run does not pick it up
— GitHub pins the originally-resolved workflow at run
creation. Without workflow_dispatch, the only way to pull the updated workflow
is a fresh push/pull_request, which forces committing an unrelated change.

Adding workflow_dispatch lets us re-trigger CI on demand against the latest
@main.

Note

Opening this PR also serves to validate reusable-workflows#74 (the fix that adds
occ upgrade after enabling the app under test, resolving the needsDbUpgrade
→ HTTP 503 failures in acceptance tests). This PR's own CI run is the first
firstrunwizard event to resolve reusable-workflows@main after that merge.

🤖 Generated with Claude Code

Add a workflow_dispatch trigger so CI can be re-run on demand against the
latest reusable-workflows@main. Reruns of an existing run pin the original
workflow resolution, so a manual dispatch (or a fresh push/PR) is the only
way to pick up a fix that landed upstream without committing unrelated
changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
@DeepDiver1975 DeepDiver1975 deleted the ci/add-workflow-dispatch branch June 29, 2026 22:10
Sign up for free to 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.

1 participant