Trigger supbase upsert on push to master instead of pull request

[bzwrk]

WHY

Summary by CodeRabbit

• Chores
  • Refined the automated deployment process to trigger on direct code updates, ensuring a more streamlined and timely integration of changes.
  • No changes affect the visible features of the app.

[linear]

DJ-2909 Change supabase upsert to trigger on push to master

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Feb 14, 2025 6:48pm
pipedream-docs	⬜️ Ignored (Inspect)			Feb 14, 2025 6:48pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Feb 14, 2025 6:48pm

[coderabbitai]

Walkthrough

The workflow configuration for pushing registry app files to Supabase has been updated. The trigger event is now set to act on a push to the master branch instead of a pull request. The configuration continues to monitor changes in files under the components/** directory, and the internal workflow steps remain unchanged.

Changes

File(s)	Change Summary
.github/.../push-registry-app-files-supabase.yaml	Modified the trigger from a pull_request to a push event on the master branch while keeping the monitored paths and job steps unchanged.

Sequence Diagram(s)

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

    Dev->>GH: Push commit to master branch
    GH->>WF: Trigger push event workflow
    WF->>WF: Checkout repository & set up environment
    WF->>SP: Upload modified files (components/**)

Loading

Possibly related PRs

• Biz/dj 2899 create a GitHub action to upsert any changed app files into #15614: Adjusted a GitHub Action workflow for pushing files to Supabase, similar in functionality to the changes in this PR.

Suggested reviewers

• dylburger

Poem

I'm a bouncy bunny, codes in my hop,
Switching the trigger, delays we now drop.
From pull requests to push, the workflow's in tune,
Digging into files under a bright GitHub moon.
Supabase receives, with precision and might,
Celebrating each change, my heart feels light! 🐇✨

---

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/push-registry-app-files-supabase.yaml (1)

15-18: Permissions Review: Evaluate Unused Scopes

The permissions block still includes pull-requests: write, though this workflow no longer triggers on pull requests. For a principle of least privilege, consider removing or reviewing this permission if it’s no longer required for the workflow tasks.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c538cba and 1b1cdaf.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• .github/workflows/push-registry-app-files-supabase.yaml (1 hunks)

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

• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base

🔇 Additional comments (1)

.github/workflows/push-registry-app-files-supabase.yaml (1)

3-9: Workflow Trigger Update: Switching from Pull Request to Push

The workflow now triggers on a push event to the master branch (while still filtering for changes under components/**). This modification precisely meets the PR objective. Please verify that this change fits your deployment strategy and that no unintended branches trigger the workflow.