mirror of https://github.com/astral-sh/uv
7a56950bab
I updated the Github Actions integration guide to run Github's `setup-python` before Astral's `setup-uv`, as `setup-uv`'s `activate-environment: true` doesn't work with the original ordering. There is a discussion about this behavior in the `setup-uv` repo [here](https://github.com/astral-sh/setup-uv/issues/479). <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary Update the documentation for the Github Actions integration. Caveat: I'm unsure if there are any other reasons where the original ordering (that is,`setup-uv` before `setup-python`) might be preferred. ## Test Plan Tested in a private Github Actions push, as documented in the aforementioned discussion on `setup-uv`'s repo. Confirmed that removing `source .venv/bin/activate` and replacing it with `activate-environment: true` now works in this ordering (but didn't work with the original ordering where `uv` installs before Github's `python`). |
||
|---|---|---|
| .. | ||
| alternative-indexes.md | ||
| aws-lambda.md | ||
| dependency-bots.md | ||
| docker.md | ||
| fastapi.md | ||
| github.md | ||
| gitlab.md | ||
| index.md | ||
| jupyter.md | ||
| marimo.md | ||
| pre-commit.md | ||
| pytorch.md | ||