This is an automated email from the ASF dual-hosted git repository.
chengpan pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 0de96b1faf Update the guidance for pinging interested parties on PRs
(#680)
0de96b1faf is described below
commit 0de96b1faf0f68e86b3a642aa7279b9bcb0dce2c
Author: David Tagatac <[email protected]>
AuthorDate: Tue Feb 24 23:57:53 2026 -0800
Update the guidance for pinging interested parties on PRs (#680)
---
contributing.md | 3 +--
site/contributing.html | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/contributing.md b/contributing.md
index 8ad11a2d0f..1d68b76959 100644
--- a/contributing.md
+++ b/contributing.md
@@ -411,8 +411,7 @@ will trigger workflows "On pull request*" (on Spark repo)
that will look/watch f
but needs to be pushed to GitHub to facilitate review, then add `[WIP]`
after the component.
1. Consider identifying committers or other contributors who have worked
on the code being
changed. Find the file(s) in GitHub and click "Blame" to see a
line-by-line annotation of
- who changed the code last. You can add `@username` in the PR description
to ping them
- immediately.
+ who changed the code last. You can add `@username` in a comment on the PR
to ping them.
1. Please state that the contribution is your original work and that you
license the work
to the project under the project's open source license.
1. The related JIRA, if any, will be marked as "In Progress" and your pull
request will
diff --git a/site/contributing.html b/site/contributing.html
index a86f932ac5..de760f3ebe 100644
--- a/site/contributing.html
+++ b/site/contributing.html
@@ -610,8 +610,7 @@ will trigger workflows “On pull request*” (on
Spark repo) that will
but needs to be pushed to GitHub to facilitate review, then add <code
class="language-plaintext highlighter-rouge">[WIP]</code> after the
component.</li>
<li>Consider identifying committers or other contributors who have
worked on the code being
changed. Find the file(s) in GitHub and click “Blame” to see a
line-by-line annotation of
- who changed the code last. You can add <code class="language-plaintext
highlighter-rouge">@username</code> in the PR description to ping them
- immediately.</li>
+ who changed the code last. You can add <code class="language-plaintext
highlighter-rouge">@username</code> in a comment on the PR to ping them.</li>
<li>Please state that the contribution is your original work and that
you license the work
to the project under the project’s open source license.</li>
</ol>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
