template / setup-python-env
AGENTS.md20 starsChanged 2 months agoApache-2.0View on GitHub
Composite action wrapping the shared CI Python setup. See README.md for usage and inputs. 1. astral-sh/setup-uv — SHA-pinned; enable-cache: true, prune-cache: true, cache-dependency-glob: "**/uv.lock". 2. actions/setup-python — SHA-pinned; python-version from the input (default "3.14"). It deliberately does not run actions/checkout (the caller does, first) and does not run uv sync (kept explicit per job so dependency groups stay visible). - Third-party uses: are pinned to a full commit SHA with a # vX.Y.Z comment, matching ../../workflows/ci.yml. - The SHAs here…
Files
setup-python-env — technical reference
Composite action wrapping the shared CI Python setup. See
README.md for usage and inputs.
Steps (in order)
astral-sh/setup-uv— SHA-pinned;enable-cache: true,prune-cache: true,cache-dependency-glob: "**/uv.lock".actions/setup-python— SHA-pinned;python-versionfrom the input (default"3.14").
It deliberately does not run actions/checkout (the caller does, first) and
does not run uv sync (kept explicit per job so dependency groups stay
visible).
Invariants
- Third-party
uses:are pinned to a full commit SHA with a# vX.Y.Zcomment, matching../../workflows/ci.yml. - The SHAs here are the single source of truth for the setup block; bump them here, not per job.
- Changing inputs or step order requires updating the "Shared setup" section of
../../workflows/AGENTS.mdin the same change.
Verification
actionlint(CIactionlintjob) validates this action and its callers.- Behavioural proof is the next CI run: GitHub Actions ordering (local action
resolves only post-checkout) cannot be exercised by local
actionlint.
In this repository42 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- fonds/AGENTS.mdAGENTS.md
- .github/actions/AGENTS.mdAGENTS.md
- .github/actions/setup-acceptance-documents/AGENTS.mdAGENTS.md
- .github/actions/setup-acceptance-fixtures/AGENTS.mdAGENTS.md
- .github/actions/setup-acceptance-model/AGENTS.mdAGENTS.md
- .github/actions/setup-docs-lint/AGENTS.mdAGENTS.md
- .github/actions/setup-native-installed-readiness/AGENTS.mdAGENTS.md
- .github/actions/upload-readiness-shards/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/ISSUE_TEMPLATE/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- infrastructure/AGENTS.mdAGENTS.md
- projects/AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- tools/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- advanced-evaluationSkill
- bdi-mental-statesSkill
- context-compressionSkill
- context-degradationSkill
- context-fundamentalsSkill
- context-optimizationSkill
- evaluationSkill
- filesystem-contextSkill
- harness-engineeringSkill
- hosted-agentsSkill
- latent-briefingSkill
- long-horizon-promptingSkill
- memory-systemsSkill
- multi-agent-patternsSkill
- project-developmentSkill
- self-improvement-loopsSkill
- tool-designSkill
- continual-learningSkill
- gauss-open-gauss-cliSkill
- infrastructure-overviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.