Skip to content

Commit a9f0a98

Browse files
authored
Updated case study because codecov was updated
1 parent 2f8bbeb commit a9f0a98

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

book/lectures/201-case_study_python.qmd

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,10 @@ jobs:
3434
run: poetry run pytest tests/ --cov={{ cookiecutter.__package_slug }} --cov-report=xml
3535

3636
- name: Use Codecov to track coverage
37-
uses: codecov/codecov-action@v3
37+
uses: codecov/codecov-action@v5
3838
with:
39-
files: ./coverage.xml # coverage report
39+
token: ${{ secrets.CODECOV_TOKEN }}
40+
files: ./coverage.xml # coverage report
4041

4142
- name: Build documentation
4243
run: poetry run make html --directory docs/
@@ -56,13 +57,17 @@ Let's answer the following questions to start better understanding the `build.ym
5657
4. What is the type of runner
5758

5859
5. What events trigger this workflow?
60+
61+
6. What secrets need to be setup?
5962
:::
6063

6164
:::{.exercise}
6265
Adding the `ci.yml` workflow to your `pypkgs*` repository
6366

6467
Let's add the `ci.yml` workflow to our `pycounts*` repository from week 1!
6568

69+
0. Setup any needed secrets for the workflow.
70+
6671
1. Go to the actions tab for your GitHub repository
6772

6873
2. Click on "*set up a workflow yourself*"

0 commit comments

Comments
 (0)