docs: add pre-commit usage with ADO Artifact feeds#39
Open
temporaer wants to merge 1 commit into
Open
Conversation
temporaer
force-pushed
the
docs/pre-commit-usage
branch
2 times, most recently
from
9a93339 to
0b381b0
Compare
Explain how to install private pre-commit hooks (Python packages) hosted on Azure DevOps Artifact feeds using the repo:local pattern with additional_dependencies and pip keyring authentication. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
temporaer
force-pushed
the
docs/pre-commit-usage
branch
from
0b381b0 to
5b4b019
Compare
sarahnlewis
approved these changes
Jun 16, 2026
jzazo
approved these changes
Jun 17, 2026
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.
Adds a Usage with pre-commit section to the README explaining how to route pre-commit's Python package installations through an ADO Artifact feed for supply-chain compliance.
Approach
Hook repositories are still cloned from GitHub via git (pinned by commit SHA) — only the pip install step is routed through the feed via keyring authentication.
What's documented
repo:entries with commit SHA pinning (notrepo: local)language: pythonhooks route through the feed; git clones still go directly to GitHubpre-commit cleanwhen credentials expireNo code changes
The keyring backend already handles pip authentication. Pre-commit calls pip in a subprocess, and pip respects
PIP_INDEX_URL+PIP_KEYRING_PROVIDER=subprocess.