Skip to content

ci: add workflow_dispatch trigger to coverage workflow #2645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
tolgaozen merged 1 commit into from
Nov 22, 2025
Merged

ci: add workflow_dispatch trigger to coverage workflow #2645

tolgaozen merged 1 commit into from
Nov 22, 2025

Conversation

@tolgaozen
Copy link
Member

@tolgaozen tolgaozen commented Nov 22, 2025 •
edited by coderabbitai bot
Loading

Summary by CodeRabbit

  • Chores
    • Enhanced workflow automation configuration to enable manual trigger capabilities alongside existing automatic triggers.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Nov 22, 2025 •
edited
Loading

Walkthrough

Added workflow_dispatch trigger to the GitHub Actions coverage workflow configuration, enabling manual workflow execution alongside existing push and pull_request event triggers.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow Configuration
.github/workflows/coverage.yml		 Added workflow_dispatch trigger to allow manual workflow invocation via GitHub UI or API in addition to automatic triggers

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 A trigger, they say, is quite grand,
When workflows dispatch by your hand!
No more waiting for push or a test,
Just click and invoke—manual's best!
Hoppy automating! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding workflow_dispatch trigger to the coverage workflow in GitHub Actions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-coverage-workflow-events
📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8928672 and 5f31a68.

📒 Files selected for processing (1)
  • .github/workflows/coverage.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Scan Container for Vulnerabilities
  • GitHub Check: Analyze (go)
  • GitHub Check: Test with Coverage
  • GitHub Check: Test with Coverage
🔇 Additional comments (1)
.github/workflows/coverage.yml (1)

2-5: LGTM! Clean addition of manual trigger capability.

The workflow_dispatch trigger is correctly added at the same indentation level as the existing push and pull_request triggers. This enables developers to manually run the coverage workflow via the GitHub Actions UI, which is a useful capability alongside automated event-driven execution.

The YAML syntax is correct and requires no configuration options for basic manual triggering.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@tolgaozen tolgaozen merged commit 0c055df into master Nov 22, 2025
13 checks passed
@tolgaozen tolgaozen deleted the update-coverage-workflow-events branch November 22, 2025 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@tolgaozen