Remove main branch filter for frontend CI workflow

[sean-zlai]

Summary

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• Chores
  • Updated automated testing triggers to run for changes on any branch, ensuring broader test coverage for frontend updates.

[coderabbitai]

Walkthrough

The changes update the GitHub Actions workflow for testing the frontend by removing branch restrictions from the push and pull_request triggers. Now the workflow runs on any branch meeting the defined file path criteria. No modifications were made to the job definitions or execution logic.

Changes

File	Change Summary
.github/workflows/test_frontend.yaml	Removed branch specifications from push and pull_request triggers to allow actions on any branch

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub
    participant WF as Workflow

    Dev->>GH: Push updates (any branch, with matching paths)
    GH->>WF: Trigger test_frontend workflow
    WF->>GH: Run frontend tests

Loading

Possibly related PRs

• Setup frontend CI #139: Introduced the workflow file; related as both modify workflow triggering conditions.
• Run github frontend workflow for files in root of frontend project (ex. package.json or other config changes) #151: Also adjusted the test_frontend.yaml file to broaden trigger conditions based on paths.

Suggested reviewers

• ken-zlai

Poem

In the land of code and commit streams,
Branch rules unwind like gentle dreams,
Tests run freely across every branch,
GitHub Actions set the new advance,
Code flows clear as a mountain stream 😊
Cheers to progress in our dev team!

Warning

Review ran into problems

🔥 Problems

GitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between c555d89 and cf55453.

📒 Files selected for processing (1)

• .github/workflows/test_frontend.yaml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/test_frontend.yaml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: enforce_triggered_workflows

---

🪧 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.

[sean-zlai]

@ken-zlai Since we stack off other branches, I couldn't think of a reason to keep the main branch filter when determining to run the frontend CI tests. For example, it would be nice if this PR was being tested

[sean-zlai]

cc: @tchow-zlai @kumar-zlai since you've created the other CI workflows

[ken-zlai]

agreed, this is nice to have