tedivm/Python Lockfile Update

This action uses pip-tools to update a project's lockfiles via a Pull Request.

Trust Signals

name	description	required	default
deploy_key	A deploy key with write access to the repository. This is required if you wish the PR to trigger workflows, as commits made with the Github Token will not. It is recommended to use a repository locked deploy key.	no	—
pr_body_text	The Pull Request comment for Pull Requests opened by this action.	yes	This Automated PR updates the requirements.txt files to the latest versions. As this is automated it should be reviewed for errors before merging.
pr_title	The Pull Request title for pull requests opened by this action.	yes	Automated Requirements File Updates
github_username	The username to use for commits from this action.	no	${{ github.actor }}
branch_prefix	A prefix used for generating branch names for the Pull Requests generated by this action.	yes	pip-update
pip_extras	A list, separated by spaces, of `extra` packages to install. For example `dev arm` to build lockfiles for dev and arm extras.	no	""
commit_message	The commit message used when committing updates to git.	yes	Automated Requirements File Updates
allow_prerelease	If set to `true` this will allow prelease versions to be included.	no	""
index_url	A repository index to use rather than PyPI. This is useful if you are using a private registry.	no	""
pip_args	Arguments to be passed through to PIP.	no	""
resolver	The dependency resolver to use. Defaults to the new backtracking algorithm- set to `legacy` for old behavior.	yes	backtracking

no outputs