Skip to content

Conversation

@probablycorey
Copy link
Contributor

@probablycorey probablycorey commented Apr 30, 2020

This adds gh pr close it looks like this 👇

image

Closes third of four features in #413

@probablycorey probablycorey requested review from mislav and vilmibm April 30, 2020 18:53
@probablycorey probablycorey self-assigned this Apr 30, 2020
@tierninho tierninho closed this May 1, 2020
@tierninho tierninho reopened this May 1, 2020
@tierninho
Copy link
Contributor

tierninho commented May 1, 2020

Works well, nice job.

Would be is it worth saying if a PR was closed and merged? As "closed" doesn't imply it was merged, it answers the question "what happened to that PR?".

Example: ! Pull request #66 is already merged and closed.

Of course this could also open the door to what type of merge: rebase, squash, etc... and users have gh pr list options as well for this.

@probablycorey
Copy link
Contributor Author

@tierninho I like the idea of including merged state. But "merged and closed" seems a little redundant? Maybe "Pull request #66 was merged" or "Pull request #66 was already closed" or is that too confusing?

@tierninho
Copy link
Contributor

"Pull request #66 was merged" or "Pull request #66 was already closed"

👍 I like this, as mine suggestion was redundant. I like this, as mine suggestion was redundant.

Copy link
Contributor

@mislav mislav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants