Skip to content

Commit c6e8e2f

Browse files
committed
updated README
1 parent 59d97af commit c6e8e2f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@
6969
<p>The one that I consider the best is the last one because it checks the coverage, execute the pytest suite, and executes the pre-commit so that at the end you can see the coverage graphs in the PR</p>
7070
<p>You need to create an account in <a target="_blank" href="https://app.codecov.io/gh">Codecov</a>, give it permission to scan repositories, get the codecov token , and store in secrets as CODECOV_TOKEN</p>
7171
<p>If you want to configure coverage to approve, you need to create a file called <code>codecov.yml</code></p>
72-
<p>You can check the file that I use in <a target="_blank" href="https://github.com/anthonypernia/setup-python-environment-with-testing-and-github-actions/blob/main/codecov.yml" ></a></p>
72+
<p>You can check the file that I use <a target="_blank" href="https://github.com/anthonypernia/setup-python-environment-with-testing-and-github-actions/blob/main/codecov.yml" >Here</a></p>
7373
<p>Here is an example of a PR using that workflow, in that case, we have some errors in pre-commit and we need to solve it</p>
7474
<img src="https://raw.githubusercontent.com/anthonypernia/setup-python-environment-with-testing-and-github-actions/main/assets/pre-commit-fail-github.png"></img>
7575
<p>When the problem is solved, when you push your code again, the tests will be updated, in that case, we need to update the test to complete the coverage</p>

0 commit comments

Comments
 (0)