Skip to content

Update the guidance for pinging interested parties on PRs #680

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pan3793 merged 1 commit into from
Feb 25, 2026
+2 −4
Merged

Update the guidance for pinging interested parties on PRs #680

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
3 changes: 1 addition & 2 deletions site/contributing.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -610,8 +610,7 @@ <h3>Pull request</h3>
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 &#8220;Blame&#8221; 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&#8217;s open source license.</li>
</ol>
Expand Down