Skip to content
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.

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

update deploy_preview run target #5660

Merged
merged 1 commit into from
Oct 14, 2024
Merged

update deploy_preview run target #5660

merged 1 commit into from
Oct 14, 2024

Conversation

lloydzhou
Copy link
Member

@lloydzhou lloydzhou commented Oct 14, 2024

πŸ’» ε˜ζ›΄η±»εž‹ | Change Type

  • feat
  • fix
  • refactor
  • perf
  • style
  • test
  • docs
  • ci
  • chore
  • build

πŸ”€ ε˜ζ›΄θ―΄ζ˜Ž | Description of Change

πŸ“ θ‘₯充俑息 | Additional Information

Summary by CodeRabbit

  • Chores
    • Streamlined deployment triggers to activate only on review requests for pull requests.
    • Maintained environment variable settings for pull request target events.

Copy link
Contributor

coderabbitai bot commented Oct 14, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the .github/workflows/deploy_preview.yml workflow file by changing the event triggers for deployment. The previous triggers related to pull request events have been replaced with a single trigger for review_requested. The step for setting environment variables retains its condition to execute only during pull_request_target events. Other steps related to the installation of the Vercel CLI, caching, and deployment logic remain unchanged.

Changes

File Change Summary
.github/workflows/deploy_preview.yml Updated event triggers to review_requested; retained environment variable settings condition.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Vercel

    User->>GitHub: Request review on pull request
    GitHub->>GitHub: Trigger deployment
    GitHub->>Vercel: Set environment variables
    GitHub->>Vercel: Install Vercel CLI
    GitHub->>Vercel: Cache dependencies
    GitHub->>Vercel: Pull environment info
    GitHub->>Vercel: Deploy project artifacts
Loading

Poem

πŸ‡ In the meadow where bunnies play,
A change was made to brighten the day.
When a review is asked, we leap and cheer,
Deploying our project, the time is near!
With Vercel in tow, we hop with delight,
For every new feature, our future is bright! 🌼


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
πŸͺ§ 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 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.

Copy link

vercel bot commented Oct 14, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
nextchat πŸ”„ Building (Inspect) Visit Preview πŸ’¬ Add feedback Oct 14, 2024 8:54am

@lloydzhou lloydzhou merged commit e34c266 into main Oct 14, 2024
3 of 4 checks passed
Copy link
Contributor

Your build has completed!

Preview deployment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant