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 d1f9967 This closes #388
discard d64339e Explicitly define section id due to kramdown id generation
changes
discard 01f1330 Update Gemfile.lock
add e1fe18b Update Gemfile.lock
add 6bd1607 Explicitly define section id due to kramdown id generation
changes
add 1501984 This closes #388: Update Gemfile.lock
add d4609c5 Rebuild site
new 51cf2e6 Update site to mention the 2 Python lint envs
new fbdc177 This closes #396
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 (d1f9967)
\
N -- N -- N refs/heads/mergebot (fbdc177)
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 2 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:
content/blog/index.html | 42 +--
content/contribute/contribution-guide/index.html | 2 +-
content/contribute/index.html | 6 +-
content/css/site.css | 349 ++++++++++-----------
content/documentation/io/io-toc/index.html | 4 +-
content/documentation/programming-guide/index.html | 242 +++-----------
content/get-started/downloads/index.html | 42 +--
content/get-started/index.html | 8 +-
src/contribute/contribution-guide.md | 3 +-
9 files changed, 267 insertions(+), 431 deletions(-)
--
To stop receiving notification emails like this one, please contact
[email protected].
