Skip to content

Update CONTRIBUTING.md and New Contributors Guide to reflect that anyone can merge PRs after checks and approvals #10123

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.

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
merged 2 commits into from
Apr 11, 2025

Conversation

jhelsby
Copy link
Contributor

@jhelsby jhelsby commented Apr 11, 2025

Summary

As discussed in this PR, anyone can merge PRs once approved and all CI checks have passed. CONTRIBUTING.md was outdated, saying only people with write-access could merge.

This change:

  • Updates CONTRIBUTING.md to reflect the fact anyone can merge their PR after required approvals and checks.
  • Adds step-by-step instructions on this to the New Contributors Guide.

Copy link

pytorch-bot bot commented Apr 11, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/10123

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 3eb0193 with merge base eeabc29 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 11, 2025
@jhelsby jhelsby changed the title Docs/jhelsby/merging p rs update Update CONTRIBUTING.md and New Contributors Guide to reflect that anyone can merge PRs after checks and approvals Apr 11, 2025
@jhelsby
Copy link
Contributor Author

jhelsby commented Apr 11, 2025

@pytorchbot label "topic: not user facing"

@jhelsby jhelsby marked this pull request as ready for review April 11, 2025 22:03
@jhelsby jhelsby requested a review from mergennachin as a code owner April 11, 2025 22:03
@byjlw
Copy link
Contributor

byjlw commented Apr 11, 2025

@pytorchbot cherry-pick --onto release/0.6 -c docs

@byjlw byjlw merged commit 409447d into pytorch:main Apr 11, 2025
4 of 6 checks passed
@jhelsby jhelsby deleted the docs/jhelsby/merging-PRs-update branch April 11, 2025 22:20
@pytorchbot
Copy link
Collaborator

Cherry picking #10123

Command git -C /home/runner/work/executorch/executorch cherry-pick -x -X theirs 409447d75a1524c1acc8f8ea894c2e13dd723a79 returned non-zero exit code 128

fatal: bad object 409447d75a1524c1acc8f8ea894c2e13dd723a79
Details for Dev Infra team Raised by workflow job

keyprocedure pushed a commit to keyprocedure/executorch that referenced this pull request Apr 21, 2025
…one can merge PRs after checks and approvals (pytorch#10123)

### Summary
As discussed in [this
PR](pytorch#10118), anyone can merge
PRs once approved and all CI checks have passed. `CONTRIBUTING.md` was
outdated, saying only people with write-access could merge.

This change:

* Updates CONTRIBUTING.md to reflect the fact anyone can merge their PR
after required approvals and checks.
* Adds step-by-step instructions on this to the New Contributors Guide.

---------

Co-authored-by: jhels <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants