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

labels: add version labels #55

Closed
wants to merge 1 commit into from
Closed

labels: add version labels #55

wants to merge 1 commit into from

Conversation

mscdex
Copy link
Contributor

@mscdex mscdex commented Jul 24, 2016

No description provided.

@mscdex
Copy link
Contributor Author

mscdex commented Jul 24, 2016

I wasn't sure exactly how to test the webhook, but going by the github webhook docs that should be the correct property for obtaining the base branch from the webhook event data.

@phillipj
Copy link
Member

I wasn't sure exactly how to test the webhook ...

Np, no one else has gotten around creating automated tests for webhooks so far - hopefully some day :) The easiest way to test webhooks locally ATM would be via SSE relay functionality.

@williamkapke could you add the necessary relay webhook to https://github.com/TestOrgPleaseIgnore/node?

@jbergstroem
Copy link
Member

Perhaps just mock the api response from the version we're talking to?

@phillipj
Copy link
Member

phillipj commented Aug 5, 2016

Yeah, I've got a branch ready to push soon which mocks every call made to GH

@jbergstroem
Copy link
Member

Awesome!

: matchAllSubSystem(filepathsChanged, limitLib)

// Add version labels if PR is made against a version branch
const m = /^(v\d+\.(?:\d+|x))(?:-|$)/.exec(baseBranch)

This comment was marked as off-topic.

@phillipj
Copy link
Member

phillipj commented Sep 5, 2016

Landed in 3a30e94

So sorry for stalling this for so long @mscdex! Included an integration test ensuring the v6.x got added when the webhook payload said the PR targeted v6.x-staging.

@phillipj phillipj closed this Sep 5, 2016
@phillipj
Copy link
Member

phillipj commented Sep 5, 2016

This is now live in production

@Fishrock123
Copy link
Contributor

Comment was ignored? :/

@phillipj
Copy link
Member

phillipj commented Sep 5, 2016

Comment was ignored? :/

@Fishrock123 sry, didn't see your comment! I'll get a PR up right away... Was this a coincident you having a look at this old & stalled PR, and me working to get it merged??

phillipj added a commit to phillipj/github-bot that referenced this pull request Sep 5, 2016
Minor adjustment to the regex matching the base branch a PR is targeted against.

Refs nodejs#55 (comment)
@mscdex
Copy link
Contributor Author

mscdex commented Sep 7, 2016

Hooray, it works!: nodejs/node#8437

@phillipj
Copy link
Member

phillipj commented Sep 8, 2016

Yiiiiiha, nice work!

@mscdex you got any objections to this
#70?

On Thursday, 8 September 2016, Brian White [email protected] wrote:

Hooray, it works!: nodejs/node#8437
nodejs/node#8437


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#55 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABLLE53ggEMENBcRs0lHpzM6S0OVjNAeks5qn0JwgaJpZM4JTqBN
.

@mscdex mscdex deleted the add-version-labels branch September 12, 2016 05:20
phillipj added a commit that referenced this pull request Oct 18, 2016
Minor adjustment to the regex matching the base branch a PR is targeted against.

Refs #55 (comment)
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.

4 participants