You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently reviews are initiated when the PR is initially opened which is good, but not great. Ideally it should also consider the first build or status checks on the PR before sending requests for the code to be reviewed. I tried various things, but failed. It would be better if the action internally was able to check whether it already sent the review, then it could be inserted into the normal build flow after all status (lint, format, build and so) are successfully completed.
It could then also be configured to re-request reviews if the repo was setup to require new reviews on new pushes.
Or is there a way to do this I was not able to figure out?
The text was updated successfully, but these errors were encountered:
I was playing with something like this which optionally executes the action. This can be inserted after the build/lint/verify steps so that only valid builds cause the notification. A user can also remove the label to cause a new notification later on (similar to draft non-draft switching)
Currently reviews are initiated when the PR is initially opened which is good, but not great. Ideally it should also consider the first build or status checks on the PR before sending requests for the code to be reviewed. I tried various things, but failed. It would be better if the action internally was able to check whether it already sent the review, then it could be inserted into the normal build flow after all status (lint, format, build and so) are successfully completed.
It could then also be configured to re-request reviews if the repo was setup to require new reviews on new pushes.
Or is there a way to do this I was not able to figure out?
The text was updated successfully, but these errors were encountered: