What you would like to be added?
I’m an external contributor to Grove, and I’ve run into this a few times already:
After opening a PR, sometimes the E2E tests fail for reasons that don’t seem related to the actual code change. It might be a flaky test, a temporary environment issue, or something else on the CI side.
When that happens, as an external contributor, I currently don’t have a good way to rerun those tests myself. I also can’t trigger something like /ok-to-test from the outside. So in practice, I end up making and pushing a meaningless code change just to get CI to run again.
It would be great if Grove could support a cleaner way for external contributors to retrigger E2E tests on their PRs without having to add unrelated commits.
Why is this needed?
Add something along the lines of what was done in PR #459, so rerunning tests for external PRs is easier and more intentional.
What you would like to be added?
I’m an external contributor to Grove, and I’ve run into this a few times already:
After opening a PR, sometimes the E2E tests fail for reasons that don’t seem related to the actual code change. It might be a flaky test, a temporary environment issue, or something else on the CI side.
When that happens, as an external contributor, I currently don’t have a good way to rerun those tests myself. I also can’t trigger something like /ok-to-test from the outside. So in practice, I end up making and pushing a meaningless code change just to get CI to run again.
It would be great if Grove could support a cleaner way for external contributors to retrigger E2E tests on their PRs without having to add unrelated commits.
Why is this needed?
Add something along the lines of what was done in PR #459, so rerunning tests for external PRs is easier and more intentional.