ci: run on PRs to all base branches

[gartnera]

The * expression is apparently not working. Remove types too since default is already opened, reopened, synchronized

Summary by CodeRabbit

• New Features
  • Streamlined pull request workflow by limiting event triggers, optimizing execution efficiency.
  • Enhanced responsiveness of the SAST linters to all pull request events, improving CI/CD pipeline performance.
• Bug Fixes
  • Adjusted workflow triggers to prevent unnecessary builds, ensuring smoother development processes.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Walkthrough

The recent changes to the GitHub Actions workflows streamline the event triggers associated with pull requests across multiple configuration files. By narrowing the conditions under which workflows are triggered, the updates aim to optimize CI/CD processes, reduce unnecessary builds, and enhance responsiveness to relevant events, particularly for the SAST linters. These modifications reflect a strategic shift toward a more efficient workflow management.

Changes

Files	Change Summary
.github/workflows/build.yml	Removed specific event triggers for the pull_request workflow, streamlining actions and reducing unnecessary builds while keeping concurrency settings intact.
.github/workflows/e2e.yml	Eliminated branches specification under the pull_request trigger, limiting workflow execution to specific branches and reducing responsiveness to others.
.github/workflows/sast-linters.yml	Removed types specification from the pull_request trigger, broadening the workflow's responsiveness to all pull request events.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant CI/CD Pipeline

    Developer->>GitHub: Create/Update Pull Request
    GitHub->>CI/CD Pipeline: Trigger Workflow
    CI/CD Pipeline->>Developer: Build Results

Loading

This diagram illustrates the high-level interaction when a pull request is created or updated, leading to the triggering of the CI/CD workflow within the GitHub Actions framework.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between dcfe022 and 9444481.

Files selected for processing (3)

• .github/workflows/build.yml (1 hunks)
• .github/workflows/e2e.yml (1 hunks)
• .github/workflows/sast-linters.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/build.yml

Additional comments not posted (2)

.github/workflows/sast-linters.yml (1)

8-8: LGTM! The removal of types specification broadens the trigger conditions.

This change ensures that the workflow responds to all pull request events by default, which aligns with the intended behavior.

.github/workflows/e2e.yml (1)

7-7: LGTM! The removal of branches specification narrows the trigger conditions.

This change ensures that the workflow is triggered for pull requests targeting only the specified branches, which aligns with the intended behavior.

[lumtis]

It's all branches

[morde08]

LGTM