Split CI workflow to prevent schedule inactivity from pausing push/PR builds

[tsegismont]

See vert-x3/issues#665

[vietj]

does this require only a commit in master branch, or does it also require commits to other branches ?

[vietj]

I am wondering also if in that case we could not have a single ci-5.x.yml file and get rid of ci-5.x-stable.yml

in the master branch, the only purpose of ci-5.x-stable.yml is to continue pull requests CI builds when we will create a new 5.x branch

[tsegismont]

does this require only a commit in master branch, or does it also require commits to other branches ?

Just in master, that's where our scheduled workflows are https://github.com/eclipse-vertx/vertx-sql-client/actions?query=event%3Aschedule

[tsegismont]

I am wondering also if in that case we could not have a single ci-5.x.yml file and get rid of ci-5.x-stable.yml

That should be possible, indeed. Would you like me to give it a try here?

[vietj]

I am wondering also if in that case we could not have a single ci-5.x.yml file and get rid of ci-5.x-stable.yml

That should be possible, indeed. Would you like me to give it a try here?

yes

did you test this change on a fork of this repo to ensure it works as expected for other branches ?

[tsegismont]

did you test this change on a fork of this repo to ensure it works as expected for other branches ?

Not sure what you mean exactly, can you elaborate?

[tsegismont]

That should be possible, indeed. Would you like me to give it a try here?

yes

Just pushed a commit for this. But we need to backport the change to 5.0. Otherwise, GH will use the workflow definition that is present in this branch.

[tsegismont]

As discussed off-list, there's no need to backport this. I'll go ahead and merge. Let's see how it goes and, if it works well, we can generalize the change through the stack.