This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
discard b19e933 This closes #578
omit 6f31911 [BEAM-5665] Exclude down website atrato.io from website checks
add 9643460 [BEAM-5667] remove gradle files from website
new 0010c04 This closes #579
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 (b19e933)
\
N -- N -- N refs/heads/mergebot (0010c04)
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 1 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:
.gradle/4.8/fileChanges/last-build.bin | Bin 1 -> 0 bytes
.gradle/4.8/fileHashes/fileHashes.bin | Bin 18547 -> 0 bytes
.gradle/4.8/fileHashes/fileHashes.lock | Bin 17 -> 0 bytes
.gradle/vcsWorkingDirs/gc.properties | 0
Rakefile | 1 -
5 files changed, 1 deletion(-)
delete mode 100644 .gradle/4.8/fileChanges/last-build.bin
delete mode 100644 .gradle/4.8/fileHashes/fileHashes.bin
delete mode 100644 .gradle/4.8/fileHashes/fileHashes.lock
delete mode 100644 .gradle/vcsWorkingDirs/gc.properties
