This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hive-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 956c513 deploy: 5780c3ccccf5e27b7859f82a2928c827467f0e03
956c513 is described below
commit 956c513804ffee3d2394e69eb47ada822f26c7bf
Author: zabetak <[email protected]>
AuthorDate: Fri Apr 18 11:21:44 2025 +0000
deploy: 5780c3ccccf5e27b7859f82a2928c827467f0e03
---
docs/latest/howtocommit_27362108/index.html | 27 +++++++++------------------
index.json | 2 +-
2 files changed, 10 insertions(+), 19 deletions(-)
diff --git a/docs/latest/howtocommit_27362108/index.html
b/docs/latest/howtocommit_27362108/index.html
index 5a4b978..dbb3ed2 100644
--- a/docs/latest/howtocommit_27362108/index.html
+++ b/docs/latest/howtocommit_27362108/index.html
@@ -165,25 +165,16 @@ ASF
<h2 id=commit>Commit</h2>
<p>When you commit/merge a Pull Request, please:</p>
<ol>
-<li>
-<p>Ensure that the Pull Request has a +1 vote, and that <strong>24 hours have
elapsed since the first +1 vote was cast</strong> on the Pull Request. Note
that this rule appears in the Hive Bylaws. Do not ignore it.</p>
-</li>
-<li>
-<p>Include the Jira issue id in the commit message, along with a short
description of the change and the name of the contributor. Be sure to get the
issue id right, as this causes Jira to link to the change in Git/Github.</p>
-<ol>
-<li>if contributor is you then add the following suffix to commit message
“(, reviewed by )”. Example: “HIVE-123. Add awesomesauce to
the optimizer. (jvs, reviewed by Ashutosh Chauhan)”</li>
-<li>if contributor is not you then add the following suffix to commit message
“( via )”. Example: “HIVE-123. Add awesomesauce to the
optimizer. (Mike Brakestoner, reviewed by Ashutosh Chauhan)”
-<ol>
-<li>Additionally: “Co-authored-by: Ayush Saxena <ayushsaxena@<a
href=http://apache.org>apache.org</a>>” can be used to attribute any
additional code contributors.</li>
-</ol>
-</li>
-</ol>
-</li>
-<li>
-<p>Resolve the issue as fixed, thanking the contributor and the reviewers.
<strong>Always set the “Fix Version”</strong> at this point, but
please only set a single fix version, the earliest release in which the change
will appear. However, if a patch is backported to a point release (such as
1.0.2) then multiple fix versions should be set so that the automated release
notes can list the Jira issue for the point release as well as the primary
release.</p>
-</li>
+<li>Ensure that the Pull Request has a +1 vote, and that <strong>24 hours have
elapsed since the first +1 vote was cast</strong> on the Pull Request. Note
that this rule appears in the Hive Bylaws. Do not ignore it.</li>
+<li>Include the Jira issue id in the commit message, along with a short
description of the change. Be sure to get the issue id right, in order to have
proper links between Jira and GitHub.</li>
+<li>Append the Pull Request id, in the commit subject to track the relation
between the commit and the respective Pull Request.</li>
+<li>Add <code>Co-authored-by: Ayush Saxena <[email protected]></code>
in the body of the message if multiple people contributed to the Pull
Request.</li>
+<li>Resolve the JIRA issue as fixed, and <strong>set the “Fix
Version”</strong> to the release in which the change will appear. If a
patch is backported to a point release (such as 1.0.2) then multiple fix
versions should be set so that the automated release notes can list the Jira
issue for the point release as well as the primary release.</li>
+<li>Thank the contributor(s), the reviewers, and the reporter of the issue (if
different from the contributor). It is easier to thank the people in GitHub by
mentioning their GitHub ids under the respective Pull Request.</li>
</ol>
-<h4 id=committing-documentation>Committing Documentation</h4>
+<p>Below you can find a sample commit message that adheres to the guidelines
outlined here.</p>
+<pre tabindex=0><code>HIVE-27424: Display dependency:tree in GitHub actions
(#5756)
+</code></pre><h4 id=committing-documentation>Committing Documentation</h4>
<p>Hive’s official documentation is hosted at <a
href=https://github.com/apache/hive>Github-Hive-Site</a>. To commit major
documentation changes you must raise a Pull Request to the hive-site repo.</p>
<p>Changes committed to the hive site repo will automatically get published
on: <a href=https://hive.apache.org/>https://hive.apache.org/</a></p>
<h2 id=backporting-commits-to-previous-branches>Backporting commits to
previous branches</h2>
diff --git a/index.json b/index.json
index dacf50f..49550e6 100644
--- a/index.json
+++ b/index.json
@@ -1 +1 @@
-[{"categories":null,"contents":"Query File Test(qtest) Query File Test is a
JUnit-based integration test suite for Apache Hive. Developers write any SQL;
the testing framework runs it and verifies the result and output.\n Tutorial:
How to run a specific test case Preparation Run a test case Tutorial: How to
add a new test case Add a QFile Generate a result file Verify the new result
file Commandline options Test options Test Iceberg, Accumulo, or Kudu
QTestOptionHandler: pre/pos [...]
\ No newline at end of file
+[{"categories":null,"contents":"Query File Test(qtest) Query File Test is a
JUnit-based integration test suite for Apache Hive. Developers write any SQL;
the testing framework runs it and verifies the result and output.\n Tutorial:
How to run a specific test case Preparation Run a test case Tutorial: How to
add a new test case Add a QFile Generate a result file Verify the new result
file Commandline options Test options Test Iceberg, Accumulo, or Kudu
QTestOptionHandler: pre/pos [...]
\ No newline at end of file
