This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git.
omit d9c3d1c Regen for commit bbc8b8cde2df7c741c82b5c7636ad590e8f5a33f
add 5c4a028 Added example of AWS Secrets Manager Properties function in
Camel-jbang DSL
add c15c727 Regen for commit 5c4a0284a7cf6b393113803b77f8a4caaeaccb54
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 (d9c3d1c)
\
N -- N -- N refs/heads/regen_bot (c15c727)
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:
.../camel-jbang-main/examples/aws-secrets-manager-properties.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
