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
It seems that CI jobs are running twice reacting on on both push and PR creation events when opening a PR, leading to unnecessary resources usage.
Outside that this can lead to confusion and adds us more error surface.
Therefore this ticket aims to prevent CI from running on push and PR creation.
The text was updated successfully, but these errors were encountered:
@ipopescu I think it is and what I have observed is that if you just specify the push as a trigger for the workflow run, then the checks for the PR do not work because Github Actions is not able to link your last push job status to the PR creation.
There must be a way to deal with this situation.
If a fix is found, you don't have to wait for the jobs to run again on the same commit after opening a PR, when they were successful when the same commit was pushed to your branch.
It seems that CI jobs are running twice reacting on on both push and PR creation events when opening a PR, leading to unnecessary resources usage.
Outside that this can lead to confusion and adds us more error surface.
Therefore this ticket aims to prevent CI from running on push and PR creation.
The text was updated successfully, but these errors were encountered: