Matthew Paravati

Hi @vim-zz, hmm maybe but if that were the case, wouldn't the estimate possibly be too long rather than too short? Also, how would that affect our files length check?

@bartkuzio, do you have `ignore_files` set in your `gitstream.cm`? I did and just removed them as a test (bc another repo here didn't ignore any files and it showed PRs...

@vim-zz just to confirm, it needs to be a new PR and not 1 we've pushed changes to since you requested this info?

@vim-zz just sent an email over. Should have all the requested info except for the number of changes lines in each file

@vim-zz the issue does not seemed resolved here. A new PR opened today is still being marked as ~1 minute review and only requiring 1 approval. I sent some more...

Awesome, thanks @vim-zz! I do see it working now! 🥳

@BenLloydPearson I've added it as a part of the collapsible text section gitstream.cm in my initial report. Is that fine?

@vim-zz thanks for the response. The `require-reviewers@v1` action was previously managed, correct? and this behavior was changed recently? Is there a different action I should/could use instead to block merging...

@vim-zz Thanks, I tried updating to using the `request-changes` action. It correctly blocked the PR once we added the label but when we removed the label, "request-changes" still shows as...

@vim-zz @BenLloydPearson thoughts on the above? Is it easier/better to create a new issue?