Add functionality for rebasebot to rebase onto viable/strict branch#78276
Add functionality for rebasebot to rebase onto viable/strict branch#78276swang392 wants to merge 6 commits intopytorch:masterfrom
Conversation
🔗 Helpful links
✅ No Failures (0 Pending)As of commit 24ad43d (more details on the Dr. CI page): Expand to see more💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
|
@pytorchbot rebase |
|
Successfully rebased |
011b435 to
6591805
Compare
.github/scripts/test_tryrebase.py
Outdated
There was a problem hiding this comment.
Can we use an older PR so we don't need to add to gql_mocks.json lol
There was a problem hiding this comment.
aka one that already existed (like would 31093 work?)
There was a problem hiding this comment.
changed the PR to 31093, but it still says that gql_mocks.json was changed
6591805 to
9a48fc5
Compare
|
@pytorchbot merge -g |
|
Hey @swang392. |
…78276) (#78276) Summary: Fixes #325 **Summary**: Currently, the pytorchbot only allows for rebasing to the master branch. These modifications add functionality for rebasing to the 'viable/strict' branch of pytorch/pytorch by adding a flag to the comment. **Test Plan:** tested manually on personal fork ([#1](swang392#1)), and included a test case in test_tryrebase.py that checks if rebasing to viable/strict branch was successful. Pull Request resolved: #78276 Approved by: https://github.com/clee2000, https://github.com/janeyx99 Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/bbb2964bd83357b6e205fb48040b3ca472ab0c46 Reviewed By: mehtanirav Differential Revision: D36707352 Pulled By: swang392 fbshipit-source-id: 20f928bd70271162d8ee0aac5274be5a0c33a636
Fixes #325
Summary: Currently, the pytorchbot only allows for rebasing to the master branch. These modifications add functionality for rebasing to the 'viable/strict' branch of pytorch/pytorch by adding a flag to the comment.
Test Plan: tested manually on personal fork (#1), and included a test case in test_tryrebase.py that checks if rebasing to viable/strict branch was successful.