Skip to content
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

Fix Buddy.works isPR because PR ids are not always ints #917

Merged
merged 4 commits into from
Sep 13, 2019

Conversation

typeofweb
Copy link
Member

@typeofweb typeofweb commented Sep 10, 2019

I was testing Buddy.works CI and it seems the integration with Danger doesn't work. I figured it's because of an incorrect assumption that PR ids are always integers. In my case, in a public GitHub repository, PR id is eg. pull/42.

I tested this and it works fine now 👍

Pinging @kristof0425 because he implemented the integration.

@@ -61,7 +61,7 @@ describe(".isPR", () => {
describe(".pullRequestID", () => {
it("pulls it out of the env", () => {
const buddyWorks = new BuddyWorks(correctEnv)
expect(buddyWorks.pullRequestID).toEqual("1799")
expect(buddyWorks.pullRequestID).toEqual("pull/1799")
Copy link
Member

@orta orta Sep 11, 2019

Choose a reason for hiding this comment

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

This will need you to return the number "1799" - so I'd check maybe for "pull" in the string and extract the number out in the BuddyWorks class 👍

Copy link
Member Author

Choose a reason for hiding this comment

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

I wasn't aware of that, it seemed to be working just fine. I'm almost certain there's another env variable which holds just the number. I'll update the PR in a few hours @orta
Thanks for review!

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated now @orta

Copy link
Member Author

Choose a reason for hiding this comment

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

BTW I was wondering if it made sense to change the return type of get pullRequestID to number? :) This way it would be clear just by looking at the definition that a number is required.

Copy link
Member

@orta orta Sep 13, 2019

Choose a reason for hiding this comment

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

Maybe it was being set from somewhere else? The GitHub API takes strings for the pull ID - likely legacy on their side, but I'm open to making them numbest so long as it's parsed back into a string in the API layers

@orta
Copy link
Member

orta commented Sep 13, 2019

Cool, thanks!

@orta orta merged commit dd5da6f into danger:master Sep 13, 2019
@peril-staging
Copy link
Contributor

peril-staging bot commented Sep 25, 2019

Thanks for the PR @mmiszy.

This PR has been shipped in v9.2.1 - CHANGELOG.

@typeofweb typeofweb deleted the fix-buddy-pr-int branch October 30, 2019 16:27
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.

2 participants