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, oeo-closure is built after every commit. This takes significant amount of time.
Maybe it is enough, if oeo-closure is only built for pull requests to the master branch or after a release.
Ideas of solution
If you already have ideas for the solution describe them here
Whether it is enough to only run the build and test steps in these cases, is probably decided by someone else - @stap-m?
But, it should be possible to integrate these conditions into the workflow.
[...] oeo-closure is only built for pull requests to the master branch or after a release.
So, both steps should no longer run e.g. on the default branch, but only
on branches associated with open pull requests targeting the default branch or
on the default branch if a new tag (e.g. v2.5.0) has been published?
Description of the issue
Currently, oeo-closure is built after every commit. This takes significant amount of time.
Maybe it is enough, if oeo-closure is only built for pull requests to the master branch or after a release.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist
The text was updated successfully, but these errors were encountered: