This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch camel-master
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git.
discard dda20e6 Sync master/camel-master run at midnight
discard 2a57fae Test for automatic sync
discard e62fb38 Fix cassandra for camel 3.5
discard cc5f4b4 Regen
discard cb8ec1f Pointing the github actions to 3.5.0-SNAPSHOT
discard bf8a898 Point to 3.5.0-SNAPSHOT
add 5a5ec1e Run both the auto sync and rebase camel-master on master in
sequence
add 66ec12e Better conditional in the rebase gh action
new 5d85c31 Point to 3.5.0-SNAPSHOT
new a5bfa92 Pointing the github actions to 3.5.0-SNAPSHOT
new 41d5d12 Regen
new 6c91063 Fix cassandra for camel 3.5
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (dda20e6)
\
N -- N -- N refs/heads/camel-master (6c91063)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/workflows/automatic-sync-camel-master.yml | 63 ----------------------
.../workflows/rebase-master-onto-camel-master.yml | 5 +-
2 files changed, 4 insertions(+), 64 deletions(-)
delete mode 100644 .github/workflows/automatic-sync-camel-master.yml
