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
discard 49a9e3c2 Regen for commit 13baaa26fb6ea294e8642c5408019009d4c51700
add 28e94935 Update team.md (#1647)
add a541deb2 Regen for commit 28e9493502758e2d39427fe7d53395d229bda464
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 (49a9e3c2)
\
N -- N -- N refs/heads/regen_bot (a541deb2)
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/community/team.md | 1 +
1 file changed, 1 insertion(+)
