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

set up pre-commit #3

merged 3 commits into from May 14, 2019


None yet
1 participant
Copy link

commented May 10, 2019

Based on the tox pre-commit setup.


  • Add dev instructions to README

This comment has been minimized.

Copy link

commented May 10, 2019

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master     #3   +/-   ##
  Coverage     100%   100%           
  Files           2      2           
  Lines          42     42           
  Branches        4      4           
  Hits           42     42
Impacted Files Coverage Δ
hypothesis_bio/ 100% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b4c568a...bbf06f9. Read the comment docs.

@luizirber luizirber force-pushed the pre-commit branch from e171311 to 705799f May 13, 2019

isort and pre-commit configs
Dev instructions in readme
use tox.ini from tox to setup more tasks

@luizirber luizirber force-pushed the pre-commit branch 9 times, most recently from 87165d8 to fb4d332 May 13, 2019

@luizirber luizirber force-pushed the pre-commit branch from fb4d332 to 95f39a1 May 14, 2019

@luizirber luizirber merged commit 933f029 into master May 14, 2019

4 checks passed

Travis CI - Branch Build Passed
Travis CI - Pull Request Build Passed
codecov/patch Coverage not affected when comparing b4c568a...bbf06f9
codecov/project 100% remains the same compared to b4c568a

@luizirber luizirber deleted the pre-commit branch May 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.