Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Support github pull request merge action #117
base: master
Are you sure you want to change the base?
Support github pull request merge action #117
Changes from 7 commits
1531c34
3f1f53e
3582ca2
4523e75
f2f8308
b4e8c67
d737085
f97ab81
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the json payload in
pr.json
is for an open pull request; therefore it should not be set tomerged: true
. I would instead suggest adding a new, real world json file and creating a new test case. I think you will find our existingmerged_at
logic works as expected if you provide it with a real world payload for a merged action.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested on my own repo, the
merged
andmerge_at
are always marked or filled in the case of merged-pr. And both not marked or filled in the case of closed-pr and opening-pr.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there may be a misunderstanding. The
pr.json
file is for anopen
pull request (thestate
field is set toopen
) which means it cannot havemerged
set totrue
. If you want to create a test case for a merged pull request, you should add a new file, for examplepr_merged.json
; this should be a real json payload captured from github, not something modified by hand.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, it the
pr.json
is for a opening-pr, then itsmerge_at
must benull
. If it is not merged (opening), how can it have a merge time... So I think something in thepr.json
must be wrong.But having another test json (maybe
pr_merged.json
) make sense.