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/polaris.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 2f631f744 deploy: a004aaeb071acbf27f9bccbcf60334f791d07ad4
2f631f744 is described below
commit 2f631f7441324901d2af7b3ef1625aa2819e758a
Author: snazy <[email protected]>
AuthorDate: Thu Oct 16 13:42:55 2025 +0000
deploy: a004aaeb071acbf27f9bccbcf60334f791d07ad4
---
community/contributing-guidelines/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/community/contributing-guidelines/index.html
b/community/contributing-guidelines/index.html
index 1dcece5d5..7f50cfdcc 100644
--- a/community/contributing-guidelines/index.html
+++ b/community/contributing-guidelines/index.html
@@ -34,6 +34,6 @@ When filing an issue, make sure to answer these five
questions:"><link rel=prelo
</span></span></code></pre></div></li><li>You may want to push your changes to
your personal Polaris fork. Git will emit a URL that you can use to create the
Pull Request. Do not create the Pull Request yet.<div class=highlight><pre
tabindex=0
style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-bash data-lang=bash><span style=display:flex><span>git push
--set-upstream your-github-accout
</span></span></code></pre></div></li></ul><h4
id=opening-a-pull-request>Opening a Pull Request</h4><ul><li>The Pull Request
summary should provide a concise summary of the change, get inspired by <a
href=https://www.conventionalcommits.org/en/v1.0.0/>Conventional
Commits</a>.</li><li>The Pull Request description should provide the background
(rationale) of the change and describe the changes in way that someone who has
no prior knowledge can understand the rationale of the change and th [...]
</code></pre>If the PR does not fully fix the issue, use <code>Related to
#123456</code> instead of <code>Fixes
#123456</code>.</li></ul><p>Tips:</p><ul><li>If the branch for your Pull
Request contains only one (squashed) commit, GitHub will populate the PR
summary and description from that single commit.</li><li>When opening a PR
consider whether the PR is “draft” or already “ready for
review”. “Draft” means work in progress, things will change,
but c [...]
-</span></span><span style=display:flex><span>git push your-github-accout
my-branch --force
+</span></span><span style=display:flex><span>git push<span
style=color:#960050;background-color:#1e0010> </span>your-github-accout
my-branch --force
</span></span></code></pre></div></li><li>Test that your changes work by
adapting or adding tests. Verify the build passes (see <code>README.md</code>
for build instructions).</li><li>If your Pull Request has conflicts with the
<code>main</code> branch, please rebase and fix the conflicts.</li><li>If your
PR requires more work or time or bigger changes, please put the PR to
“draft” state to indicate that it is not meant to be
“thoroughly” reviewed at this point.</ [...]
The discussion on the dev mailing list should happen before having a
“ready-for-review” Pull Request.</li><li><code>git log</code> can
help you find the original/relevant authors of the code you are modifying. If
you need, feel free to tag the author in your Pull Request comment if you need
assistance or review.</li><li>Do not re-create a pull-request for the same
change. Use one Pull Request related to the same change(s). The purpose here is
to keep the history and all comme [...]
\ No newline at end of file
