docs: add documentation for the update_manager's primary_branch option
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
This commit is contained in:
parent
cd4641f959
commit
94ed9fbd7f
|
@ -388,6 +388,10 @@ origin:
|
||||||
# be be viewed by navigating to your repository and running:
|
# be be viewed by navigating to your repository and running:
|
||||||
# git remote -v
|
# git remote -v
|
||||||
# This parameter must be provided.
|
# This parameter must be provided.
|
||||||
|
primary_branch:
|
||||||
|
# The name of the primary branch used for release code on this repo. This
|
||||||
|
# option allows clients to specify 'main', or their own unique name, as
|
||||||
|
# the branch used for repo validity checks. The default is master.
|
||||||
env:
|
env:
|
||||||
# The path to the client's virtual environment executable on disk. For
|
# The path to the client's virtual environment executable on disk. For
|
||||||
# example, Moonraker's venv is located at ~/moonraker-env/bin/python.
|
# example, Moonraker's venv is located at ~/moonraker-env/bin/python.
|
||||||
|
|
Loading…
Reference in New Issue