🦩 Setup: Flamingo Code Review - #325
Closed
flamingo[bot] wants to merge 1 commit into
Closed
Conversation
This workflow enables automated code review using the 🦩 Flamingo Code Review pipeline. It runs on pull_request and repository_dispatch events triggered by the multi-platform-hub. Rules are fetched at run time and are hash-addressed, so a rule change needs no update to this file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🦩 Flamingo Code Review Setup
This PR adds the GitHub Actions workflow required for automated code review.
What this workflow does
The 🦩 Flamingo Code Review pipeline reviews this repository against the org rule corpus:
Per-repo settings (blocking vs observe, models, locale) live in the hub admin and are read at run time — this file does not change when they do. The workflow holds no push credential: fix PRs are opened by the hub.
Setup steps
After merging this PR, the workflow needs repository secrets to run. The dashboard provisions them for you, you don't paste them by hand.