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 8ed8fc8 This closes #415
discard 9990581 Fix tox lint command in contribution guide
new 3fbfbba [BEAM-3252] Updating contributor's guide to reference Gradle.
new e94af43 Fix project names to reflect changes required for release.
new 0d4a0ce Drop using gradle clean in favor of --rerun-tasks
new 47ff7df [BEAM-3252] Adding a step to the IntelliJ setup for gradle.
new 87827ed [BEAM-3252] Removing Annotation Processing section.
new 00f4cf0 Stop recommending we use auto-import
new cf87f92 Update checkstyle comment to correspond to the current version
new e0a3a96 This closes #414
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 (8ed8fc8)
N -- N -- N refs/heads/mergebot (e0a3a96)
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 8 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/contribute/contribution-guide/index.html | 2 +-
src/contribute/contribution-guide.md | 8 ++---
src/contribute/intellij.md | 31 ++++++++++--------
src/contribute/maturity-model.md | 2 +-
src/contribute/runner-guide.md | 40 ++++++++----------------
src/contribute/testing.md | 37 +++++++++-------------
6 files changed, 52 insertions(+), 68 deletions(-)
To stop receiving notification emails like this one, please contact