ci: re-run semantic PR workflow when PR is renamed

[fadeev]

Summary by CodeRabbit

• New Features
  • GitHub Actions workflow now triggers on pull request edits, enhancing automation for semantic pull requests.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces a minor modification to the GitHub Actions workflow configuration for semantic pull request validation. Specifically, the workflow now includes the edited event type in the pull_request triggers, expanding the workflow's execution scope to capture changes made to existing pull requests in addition to the previously supported events like opening, synchronizing, or reopening.

Changes

File	Change Summary
.github/workflows/semantic-pr.yaml	Added edited event type to pull_request triggers

Sequence Diagram

sequenceDiagram
    participant PR as Pull Request
    participant Workflow as Semantic PR Workflow
    
    alt Pull Request Opened
        PR ->> Workflow: Trigger workflow
    end
    
    alt Pull Request Synchronized
        PR ->> Workflow: Trigger workflow
    end
    
    alt Pull Request Edited (New Behavior)
        PR ->> Workflow: Trigger workflow
    end

Loading

The sequence diagram illustrates the expanded trigger conditions for the semantic pull request workflow, now including the edited event alongside existing event types.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/semantic-pr.yaml (1)

12-12: LGTM! Consider adding a comment for clarity.

The addition of the edited event type is appropriate for re-running semantic validation when PR titles are modified. This ensures continuous compliance with semantic versioning conventions.

Consider adding a YAML comment to document the purpose of each trigger:

    types:
      - synchronize  # When PR branch is updated
      - opened      # When PR is created
      - reopened    # When PR is reopened
      - ready_for_review  # When PR moves from draft
-      - edited
+      - edited     # When PR title/body is modified

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 785f106 and 6f43ad9.

📒 Files selected for processing (1)

• .github/workflows/semantic-pr.yaml (1 hunks)