Camel-master: Let's change the gh action to be triggered when a push on master has been done

[oscerd]

Otherwise it will be a mess to rebase if the job fails multiple times.

[oscerd]

After some work I was able to make the backport gh action works on this repository. So now, each time we open a PR on master we need to add the label "backport camel-master" and/or if it is a bug fix for 0.7.x "backport camel-kafka-connector-0.7.x", this will create a PR automatically on the selected branches.

The rebase job was too buggy because of the docs generation. In this way we should be sure we are backporting the needed bits and then regen the documentation. I removed the rebase camel-master job and I think we should do like the regen job we have on camel.

@valdar @orpiske FYI

[valdar]

Ok thanks for the effort in this specially for the LTS branches!

What would be the envisioned work-flow then? Backporting from master to camel-master then when we align camel version to the new one? merge of camel-master in master?

[oscerd]

Yes Il lun 1 feb 2021, 09:45 Andrea Tarocchi <notifications@github.com> ha scritto:

…

Ok thanks for the effort in this specially for the LTS branches! What would be the envisioned work-flow then? Backporting from master to camel-master then when we align camel version to the new one? merge of camel-master in master? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#939 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABG6XV3S43YDQCFT3XOH5HDS4ZS3JANCNFSM4WZHWSIQ> .

[orpiske]

Thanks for this @oscerd! It is really cool and I think it makes it easier for us to make sure the patches go to the right branches at the right time.