Repository navigation
👷 ci: run the uvx self-test outside a Python project - #58
Merged
Merged
Conversation
Since #43 added a root pyproject.toml, the uvx self-test ran from the repository root and took the uv run path. Run it in a fresh git repository with a minimal pre-commit config and force uv-install: true so both stay covered.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Projects without a
pyproject.tomlget the Action'suvxpath, but CI stopped running that path when #43 added a tool-onlypyproject.tomlat the repository root. The Action picks its path by whetherpyproject.tomlexists in the workspace, so the🧪 Self-test with uvxjob has runuv runever since. A regression in theuvxpath could ship unnoticed. 🔍The
uvxjob no longer checks out this repository. It starts from an empty git repository holding only a minimal pre-commit configuration, so the Action sees no Python project. The job also setsuv-install: 'true', which makes the Action install uv itself rather than rely on detection. Theuv runjob keeps its generated project and the external-uv job keepsuv-install: 'false', so each of the three paths has its own job.Nothing changes for users of the Action.