-
Notifications
You must be signed in to change notification settings - Fork 61
fix: close pr issues and stop running handlers twice #728
fix: close pr issues and stop running handlers twice #728
Conversation
✅ Deploy Preview for ubiquibot-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Update here? |
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.
can you rework gitLinkedPrParser
to return an array of PRs and move other functionality (like retrieving PR and checking merged date to get latest merged PR) outside the function. basically you are merging your work into gitLinkedPrParser
and then removing gitIssueParser
I don't understand what you mean by get it outside the function |
functions calling |
Done, check it out @whilefoo |
Co-authored-by: whilefoo <[email protected]>
Co-authored-by: whilefoo <[email protected]>
Co-authored-by: whilefoo <[email protected]>
Co-authored-by: whilefoo <[email protected]>
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.
can you post QA?
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.
Looks good to me
I have QA in description |
@0xcodercrane ping |
Resolves #710 and #716
QA: Seprintour-Test/test#22
Steps:
closePullRequestForAnIssue
was called twice, i removed it from the unassign function so unassigning is now certain (no blocking request, closing PRs by looping was pretty intensive)Refactored
closePullRequestForAnIssue
to use the gitIssueParser to fetch the exact PR open for an issue instead of looping all PRs. (Closing is more certain and 1 memory intensive task down)