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

KeywordBear: Handle empty keywords #1695

Merged
merged 2 commits into from
May 11, 2017

Conversation

meetmangukiya
Copy link
Member

If setting keyword is used in coafile and not assigned, then keywords
is an empty list, which leads to construction of regex r'()' which
matches all the letters, hence yielding false results.

Fixes #1689

For short term contributors: we understand that getting your commits well
defined like we require is a hard task and takes some learning. If you
look to help without wanting to contribute long term there's no need
for you to learn this. Just drop us a message and we'll take care of brushing
up your stuff for merge!

Checklist

  • I read the commit guidelines and I've followed
    them.
  • I ran coala over my code locally. (All commits have to pass
    individually.
    It is not sufficient to have "fixup commits" on your PR,
    our bot will still report the issues for the previous commit.) You will
    likely receive a lot of bot comments and build failures if coala does not
    pass on every single commit!

After you submit your pull request, DO NOT click the 'Update Branch' button.
When asked for a rebase, consult coala.io/rebase
instead.

Please consider helping us by reviewing other peoples pull requests as well:

The more you review, the more your score will grow at coala.io and we will
review your PRs faster!

If setting keyword is used in coafile and not assigned, then keywords
is an empty list, which leads to construction of regex `r'()'` which
matches all the letters, hence yielding false results.

Fixes coala#1689
@meetmangukiya
Copy link
Member Author

ack 2221295

@@ -1,3 +1,11 @@
coala-bears 0.10.2
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 assume since we are backporting we are making a release, hence added the release notes.

Copy link
Member Author

Choose a reason for hiding this comment

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

and again I raise a conflict for myself :P

Copy link
Member

Choose a reason for hiding this comment

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

erm I mean add to 0.11 0.10 neds to be assessed (probably needed too)

@sils
Copy link
Member

sils commented May 9, 2017

ack 2221295 86127b9

@sils
Copy link
Member

sils commented May 9, 2017

@Mixih this needs to be forward ported to 0.11 and master right?

@meetmangukiya
Copy link
Member Author

@sils, no, it is in master and also release branch

@jayvdb
Copy link
Member

jayvdb commented May 11, 2017

@rultor merge

@rultor
Copy link

rultor commented May 11, 2017

@rultor merge

@jayvdb OK, I'll try to merge now. You can check the progress of the merge here

@rultor rultor merged commit 86127b9 into coala:release/0.10 May 11, 2017
@rultor
Copy link

rultor commented May 11, 2017

@rultor merge

@jayvdb Done! FYI, the full log is here (took me 1min)

@meetmangukiya
Copy link
Member Author

@Mixih this being merged, how do we manage and synch relnotes across releases or in master?

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

Successfully merging this pull request may close these issues.

6 participants