Repository navigation
feature/expand-review-scope: Adding review scope parameter - #38
jroachgolf84 wants to merge 2 commits into
Conversation
Otto ReviewAdds 1 major issue found The scoping pipeline is well put together. Filtering happens before the line cap, the inline-comment filter runs against the scoped diff, the empty-diff check now runs before scoping, and the |
…atform-engineer and devops-engineer
|
@milton-li - do you think it's going to make sense to update the |
|
Closing this in favor of: #39 (review) |
Description
This PR adds a
review-scopeparameter that allows for a user to determine what Otto should consider. There are four options added as part of this PR:entire-repo: default value, evaluates diffs across entire repoairflow: just diffs in Airflow projectdata-engineer: diffs in Airflow project + things like SQL files, etc.platform-engineer: Terraform, IaC, etc.Related Issue(s)
No related issues.
Breaking Change?
No, this is not a breaking change.
Checklist
README.mdand theaction.yamlinput/output descriptions if the action's interface changedLint YAMLpassese2e/harness (or explained why that wasn't possible)