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

PostMissingPR - No PR link required when the patch is hosted in other SCM #28

Closed
elguardian opened this issue Mar 16, 2016 · 3 comments
Closed

Comments

@elguardian
Copy link

This happens when the PR is attached as a patch to the BZ because the SCM is the SVN (jboss-web project)

@rpelisse
Copy link
Contributor

Hi Enrique,

Do you mean it should be a check somehow or are you refering to any issue with an existing check ?

@elguardian
Copy link
Author

they should be removed. Right now there bugclerk rise an error and adds a comment to the BZ when the bz is correct. POST + patch attached.

@rpelisse
Copy link
Contributor

OK, first, as you did not answer to that, I'm going to assume you are talking about the check called 'PostMissingPR'.

Right now there bugclerk rise an error and adds a comment to the BZ when the bz is correct

OK, that what we called a False +, meaning that a check is reporting an issue where there is not. There are a bit annoying, but in this case, they are not so common. I think up until know I got less 5 occurences of such False + for this check.

I think it's not a high price to pay in exchange for all the time the check is actually correct. The check actually catch me forgetting to add the PR to a BZ probably as much.

Also, given the fact that there is a workaround (you can add a comment for BugClerk to NOT report this issue, if you know your BZ will look errrounous), I honestly it's fair.

@rpelisse rpelisse changed the title No pr link required when the patch is hosted in other SCM PostMissingPR - No PR link required when the patch is hosted in other SCM Mar 17, 2016
rpelisse added a commit to rpelisse/bug-clerk that referenced this issue Feb 3, 2017
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

No branches or pull requests

2 participants