This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1fb9c77 Publishing website 2019/03/01 11:30:20 at commit 171f9bf
1fb9c77 is described below
commit 1fb9c77b137f79176073a0d77075e53fd1276cbc
Author: jenkins <[email protected]>
AuthorDate: Fri Mar 1 11:30:20 2019 +0000
Publishing website 2019/03/01 11:30:20 at commit 171f9bf
---
website/generated-content/contribute/ptransform-style-guide/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/website/generated-content/contribute/ptransform-style-guide/index.html
b/website/generated-content/contribute/ptransform-style-guide/index.html
index b8163ad..7bb4ce3 100644
--- a/website/generated-content/contribute/ptransform-style-guide/index.html
+++ b/website/generated-content/contribute/ptransform-style-guide/index.html
@@ -310,7 +310,7 @@ limitations under the License.
<p>Be consistent with prior art:</p>
<ul>
- <li>Adhere to <a href="/contribute/design-principles/">Beam design
principles</a>.</li>
+ <li>Please read the <a href="/contribute/">contribution guide</a>.</li>
<li>If there is already a similar transform in some SDK, make the API of
your transform similar, so that users’ experience with one of them will
transfer to the other. This applies to transforms in the same-language SDK and
different-language SDKs.
<em>Exception:</em> pre-existing transforms that clearly violate the current
style guide for the sole reason that they were developed before this guide was
ratified. In this case, the style guide takes priority over consistency with
the existing transform.</li>
<li>When there is no existing similar transform, stay within what is
idiomatic within your language of choice (e.g. Java or Python).</li>
