Skip to content

Commit

Permalink
fix napari repo path to constraints (#290)
Browse files Browse the repository at this point in the history
# References and relevant issues
Fix failing deployment:
https://github.com/napari/docs/actions/runs/7093394130/job/19306680514
caused by #287

# Description
In the deploy workflow, napari is cloned into napari-repo:
`path: napari-repo  # place in a named directory`
fixing that here so that the constraints path in the ENV variable is
also using napari-repo and not napari.
Obviously overlooked this difference when reviewing
#287
Yet another reason to use just one workflow,
#284
  • Loading branch information
psobolewskiPhD authored Dec 5, 2023
1 parent 53a292f commit 0c7029e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/deploy_docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ jobs:
env:
GOOGLE_CALENDAR_ID: ${{ secrets.GOOGLE_CALENDAR_ID }}
GOOGLE_CALENDAR_API_KEY: ${{ secrets.GOOGLE_CALENDAR_API_KEY }}
PIP_CONSTRAINT: ${{ github.workspace }}/napari/resources/constraints/constraints_py3.10_docs.txt
PIP_CONSTRAINT: ${{ github.workspace }}/napari-repo/resources/constraints/constraints_py3.10_docs.txt
with:
# the napari-docs repo is cloned into a docs/ folder, hence the
# invocation below. Locally, you should simply run make docs
Expand Down

0 comments on commit 0c7029e

Please sign in to comment.