Skip to content

ci: add workflow_dispatch to allow on-demand runs (browser SonarQube scan)#61

Merged
wolpert merged 1 commit into
mainfrom
ci-manual-trigger
Jun 13, 2026
Merged

ci: add workflow_dispatch to allow on-demand runs (browser SonarQube scan)#61
wolpert merged 1 commit into
mainfrom
ci-manual-trigger

Conversation

@wolpert

@wolpert wolpert commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Adds a workflow_dispatch trigger to the CI workflow so it can be run on demand against any ref:

gh workflow run ci.yml --ref main

Why

The workflow only fired on push/pull_request to main, so there was no way to re-trigger the browser-SDK SonarQube scan without pushing a commit. This is needed to test SonarCloud project/setting changes (see #60) without churning commits.

Also

The SonarQube step's if: guard (push or same-repo PR) would have skipped the scan on a workflow_dispatch run, so it's extended to include github.event_name == 'workflow_dispatch'. Manual and push runs both have SONAR_TOKEN available; fork PRs are still excluded.

No other behavior changes.

🤖 Generated with Claude Code

… demand

The CI workflow only triggered on push/PR to main, so there was no way to
re-run the browser-SDK SonarQube scan without pushing a commit (e.g. to test
a SonarCloud project/setting change). Add a workflow_dispatch trigger
(`gh workflow run ci.yml --ref main`) and extend the SonarQube step's guard to
fire on manual runs too — otherwise the existing push/same-repo-PR condition
would skip the scan on a dispatch run.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@wolpert
wolpert merged commit 539316c into main Jun 13, 2026
5 checks passed
@wolpert
wolpert deleted the ci-manual-trigger branch June 13, 2026 14:13
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