Are there any settings for not requiring review of files that only have base commit changes? We're getting some review fatigue from developers e.g. open PR, reviewer reviews all files, author merges the target branch, and the author asks the reviewer on slack to rubber stamp the slew of files that only have base commit changes.
baseCommitSha in the completion condition input but I suspect that it can't be used to detect when a file only has base commit changes since it was last reviewed. Any ideas?
?debug=modelappended and report the value of
/queues/githubPullRequestSyncin the Firebase console to see if any tasks have been attempted a large number of times. (For the review that just won't resync, it's also possible that you've run into a fatal crash driven by the data specific to that PR, so the task can't complete. You should look for "Repeatedly failed to process event" in the logs.)
Timed out while waiting on cache-osl6528-OSL
Reviewed 5 of 5 files at r1.) so I'm wondering if there are any alternatives available or on the roadmap.
REVIEWABLE_ANALYTICS_URL. Events are posted in a JSON format that roughly follows Segment's tracking spec so there are likely tools that will be able to consume it directly (it's the closest to a "standard" I could find). I'd also be able to add more events pretty easily, architecture permitting.
I was originally thinking that number of files reviewed would be useful but we can probably use number of PRs as a reasonable proxy and use a third party solution for that. Maybe this one? https://github.com/Kimi-Gao/github-pr-analysis