-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace integration test review trigger with manual trigger #595
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## development #595 +/- ##
===============================================
- Coverage 71.67% 65.20% -6.47%
===============================================
Files 37 37
Lines 3064 3064
Branches 596 596
===============================================
- Hits 2196 1998 -198
- Misses 765 981 +216
+ Partials 103 85 -18 ☔ View full report in Codecov by Sentry. |
I was looking at our setup, and I think the funny business might be coming from our if statement: My plain text of this logic is to run the test if (1) it's not a fork AND (2) it's (a) not a PR review OR (b) it's approved. I'm not sure why condition (a) is in there, since we're using the |
@mfisher87 Any further thoughts on this? |
Maybe we should close the PR? Things seem to be working well anyway right now. Can always come back to it :) |
Strong disagree. The Integration Tests are being triggered far more often than they should be. |
When are they being triggered that you don't want them triggered? I've been struggling with them not being triggered when I do want them to be triggered. Do you think this manual triggering approach is the way forward for now? |
We decided today to avoid the rabbit hole of GitHub Actions debugging and disable the integration test merge requirement and stop running integration tests on approval for now due to finnickiness of the current config (#603). I'm sure we can figure it out eventually :) |
@JessicaS11 I think we should remove the
pull_request_review
trigger and logic. I don't know what we need to get this right, so I replaced it with a manual trigger. This will help us get PRs moving again. What do you think?TODO: