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
As mentioned in #1320, there's not currently a known way to easily re-run the Github Actions tests if the target (usually dev) gets updated while the desired pull request remains stagnant (tests are only triggered by direct commits to the pull request).
I think the only way to re-trigger the test if the target gets updated is to:
There's actually an option to re-run the tests but ONLY IF THEY FAIL for some reason
Push an empty commit, but then you have to squash/rebase and it's a lot of work
I've noticed from WFDB-Python that rebasing on dev then force pushing also re-triggers the test even though, likely, nothing directly related to the pull request changes
So yeah, not ideal at the moment so let's figure out if there's a better way!
The text was updated successfully, but these errors were encountered:
As mentioned in #1320, there's not currently a known way to easily re-run the Github Actions tests if the target (usually
dev
) gets updated while the desired pull request remains stagnant (tests are only triggered by direct commits to the pull request).I think the only way to re-trigger the test if the target gets updated is to:
dev
then force pushing also re-triggers the test even though, likely, nothing directly related to the pull request changesSo yeah, not ideal at the moment so let's figure out if there's a better way!
The text was updated successfully, but these errors were encountered: