This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel-website.git
omit cf6c9b50 Regen for commit 72bf24bd943c1e1f59dadecc953e130a5c8d19a8
add d920d6d1 Add Flinkflow to open source projects using Apache Camel
add 4d66188b chore: use 1,500+ contributors (git shortlog main-branch
count)
add d8d564a9 Regen for commit 4d66188bb14aa12b8a36a61f1a6e6cfd45b9ef97
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 (cf6c9b50)
\
N -- N -- N refs/heads/regen_bot (d8d564a9)
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.
No new revisions were added by this update.
Summary of changes:
content/blog/2026/06/camel-by-the-numbers/index.md | 8 ++++----
content/community/user-stories.md | 1 +
2 files changed, 5 insertions(+), 4 deletions(-)
