-
Notifications
You must be signed in to change notification settings - Fork 82
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
chore(CI): Checkout pr branch when event is issue_comment #2754
Conversation
https://github.com/alessbell/pull-request-comment-branch is not actively maintained and falls behind its original one. Can we fork and maintain one forked from https://github.com/xt0rted/pull-request-comment-branch, and propose the feature we desired to https://github.com/xt0rted/pull-request-comment-branch |
xt0rted/pull-request-comment-branch#356 Someone has created a pull request for this. But the repo owner hasn't dealt with it yet. |
Got it, if it is possible to fork xt0rted/pull-request-comment-branch#356 and adopt updates from alessbell/pull-request-comment-branch, and keep the forked repo synced periodically. The main problem of alessbell/pull-request-comment-branch is that it's not actively maintained |
Gotcha, I will try. |
d044e68
to
a077b96
Compare
Pull request was converted to draft
3ffdf55
to
ae7eb69
Compare
@Keith-CY @homura @WhiteMinds Please have a review |
ae7eb69
to
788872a
Compare
Because the
outputs.ref
is the fork repo's branch name. So we should add the repo parameter forcheckout
action when the event isissue_comment
.Examples:
Trigger by push: https://github.com/yanguoyu/neuron/actions/runs/5419801750
Trigger by issue_comment with current repo: pr, action: https://github.com/yanguoyu/neuron/actions/runs/5441117221
Trigger by issue_comment with fork repo: pr, action: https://github.com/yanguoyu/neuron/actions/runs/5441115012