-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Catch and raise merge conflicts #55
Conversation
621cb73
to
8ca8330
Compare
4d66796
to
8acdb59
Compare
Looks like this needs some tweaks. Please see PR ( #68 ). |
@@ -14,6 +14,20 @@ def test_cli_success_bad(self): | |||
out, _ = child.communicate() | |||
self.assertEqual(child.returncode, 0, out) | |||
|
|||
def test_cli_success_conflict_ok(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general please try to avoid these kind of tests where possible - they should be used only if we are unable to ensure coverage through unit testing.
No action needed on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By which you are meaning CLI tests? The main reason I added these was to ensure some uncaught exception wouldn't propagate out. Though maybe we have already covered that case well enough.
Closes #51
This checks to see if a PR will have merge conflicts and raises an error if it does. This should help the occasional confused or git tormented person find their way back to a mergeable PR. It also saves us from linting things when they are in a non-functioning state. After all we would not otherwise know there was a merge conflict. Testing occurs in PRs ( #56 ) and ( #57 ).