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

Make test_target less strict with git #79

Closed

Conversation

rico-chet
Copy link

An expectation of the test_target is that git prints a specific
error message when run outside a workdir. This message was changed in
one of the last git releases, so the test fails.

Make the test_target less strict regarding the message content, just
looking for the 'not a git repository' ought to be enough.

Fixes #78 for me

…vers#76)

- Various text fixes all over
- Enable lint tests for Python 3.6
- Fix some pylint warnings
- Ignore pylint errors for bad options
- Use unittest2 only for Python 2
- Test Python 3.7 in Travis
- Integration Tests: Introduce assertEqualStdout
- Activate all integration tests in Travis
- Update dependencies in requirements.txt
@rico-chet rico-chet force-pushed the fix-target-test-too-strict branch from 87136e1 to 98fb940 Compare January 24, 2019 22:31
An expectation of the `test_target` is that `git` prints a specific
error message when run outside a workdir. This message was changed in
one of the last `git` releases, so the test fails.

Make the `test_target` less strict regarding the message content, just
looking for the 'not a git repository' ought to be enough.
@jorisroovers
Copy link
Owner

This PR adjusted the test while the issue was really with the underlying gitlint code.
I believe f50e439 fixed this issue.

Currently working on v0.11.0 which includes this fix, will be out today. Closing this PR.

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