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

Create trigger_clean_build.yml #1988

Merged
merged 1 commit into from
Sep 6, 2024
Merged

Conversation

m3taphysics
Copy link
Collaborator

@m3taphysics m3taphysics commented Sep 6, 2024

What does this PR change?

Allows you to trigger a clean rebuild on an existing PR

How to test the changes?

  1. Launch the explorer
  2. ...

Our Code Review Standards

https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

Summary by CodeRabbit

  • New Features
    • Introduced a new GitHub Actions workflow named "Trigger Clean Build" for manually initiating clean builds for specific pull requests.
    • Streamlined the integration and testing process by allowing users to specify a pull request number for targeted builds.

Signed-off-by: Ashley Canning <[email protected]>
Copy link

coderabbitai bot commented Sep 6, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

A new GitHub Actions workflow named "Trigger Clean Build" has been introduced. This workflow can be manually triggered through the GitHub interface, allowing users to specify a pull request (PR) number. It includes steps to check out the code, retrieve the associated branch from the PR, and trigger a Unity Cloud Build workflow for a clean build.

Changes

Files Change Summary
.github/workflows/trigger_clean_build.yml New workflow created for manually triggering clean builds for specific pull requests.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Actions
    participant API
    participant Unity

    User->>GitHub: Trigger Clean Build
    GitHub->>Actions: Start workflow
    Actions->>Actions: Checkout code
    Actions->>API: Get PR branch
    API-->>Actions: Return branch name
    Actions->>Unity: Trigger clean build with branch name
Loading

🐰 "In the meadow, a change did bloom,
A workflow to clear the build's dark gloom.
With a PR number, just a click away,
A clean build awaits, hip-hip-hooray!
Hops of joy in the code so bright,
Let's build together, from morning till night!" 🌼


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>.
    • 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 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
Contributor

github-actions bot commented Sep 6, 2024

badge

New build in progress, come back later!

@m3taphysics m3taphysics merged commit f0784d7 into main Sep 6, 2024
3 of 5 checks passed
@m3taphysics m3taphysics deleted the fix/enable-trigger-clean-build branch September 6, 2024 19:32
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