This is an automated email from the ASF dual-hosted git repository.
tobous pushed a change to branch exit-cleanly-if-nothing-to-deploy
in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git.
discard f5d09d8 Only try to publish results if there are any changes
omit b634562 Split up publishing stage of recreate action into multiple
steps
omit fe00d30 Split up publishing stage of deploy action into multiple steps
omit 0c35802 Set 'bash' as the default shell for all deploy tasks
omit fcb8259 Capitalize short sha env name in deploy actions
omit 8f58ad9 Use GitHub action env field to declare publish branch name
omit 5bc7cd5 Ensure that all changes are staged by deploy action
add b10cf7b Set up branch protection for the 'publish' branch
add f9f5025 Ensure that all changes are staged by deploy action
add 333cc08 Use GitHub action env field to declare publish branch name
add 0fb69e6 Capitalize short sha env name in deploy actions
add 86ef00b Set 'bash' as the default shell for all deploy tasks
add c626e5d Split up publishing stage of deploy action into multiple steps
add fa61794 Split up publishing stage of recreate action into multiple
steps
add 20b26aa Only try to publish results if there are any changes
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 (f5d09d8)
\
N -- N -- N refs/heads/exit-cleanly-if-nothing-to-deploy
(20b26aa)
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:
.asf.yaml | 6 ++++++
1 file changed, 6 insertions(+)
