-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
does not support "[WIP]"? (update: it of course does!) #97
Comments
Hi @myakura, I’m pretty sure that it will it supports having /\b(wip|do not merge|work in progress)\b/i.test('[WIP]') // returns true I also tested it here and it works as expected: gr2m/sandbox#41 |
Do you have a pull request in a public repository where it does not work? Can you give me a link to it? |
@gr2m oops. lemme double check! |
hmm. so I checked again with some repos (public & private in different orgs) and this time it worked...! Anyways, sorry for confusion. apologies. Oh. I should've said this in the very first. Thanks for the app! This is really useful :-) |
Okay, it looks like the bot doesn't work on PRs that already have the keywords before installing the app. Is that an intended behavior? |
The app only sets the status when a PR gets changed. It doesn’t check existinf PRs. But that might be a good idea :) |
@gr2m thanks! |
closing in favor of #98 |
I see a lot of issues using wip keywords wrapped in brackets (e.g "[WIP]"). However, the current code to check whether the issue is a work in progress it does not support that pattern.
app/lib/handle-pull-request-change.js
Lines 47 to 49 in 88f6c67
Notice the leading
\b
. It doesn't treat brackets as word boundaries so it fails to catch issues titled "[WIP] blah".The text was updated successfully, but these errors were encountered: