dcloud git repositories updateChange description, visibility, default branch or archive state
Synopsis
dcloud git repositories update repoId [flags]Arguments
<repoId>Requiredstring
Also accepted as
--repo-id. Constraints: uuid
Flags
--descriptionOptionalstring
One line about the repository, shown in lists and the About column
Constraints: max 500 chars
--homepageOptionalstring
The About link (http or https); null removes it
Constraints: url, max 300 chars
May be null.
--topicsOptionalarray of string
Topics: lowercase letters, digits and hyphens, at most 20
Constraints: /^[a-z0-9][a-z0-9-]{0,49}$/
--visibilityOptionalenum
Who can see it; making it public also needs git:PublishRepository
One of:
private,internal,public--default-branchOptionalstring
The branch clones check out and pull requests target by default
Constraints: 1-100 chars
--is-archivedOptionalboolean (--is-archived / --no-is-archived)
true archives it (read-only: pushes, merges and edits refused); false unarchives
--allow-merge-commitOptionalboolean (--allow-merge-commit / --no-allow-merge-commit)
Pull requests may merge with a merge commit
--allow-squash-mergeOptionalboolean (--allow-squash-merge / --no-allow-squash-merge)
Pull requests may be squash-merged
--allow-rebase-mergeOptionalboolean (--allow-rebase-merge / --no-allow-rebase-merge)
Pull requests may be rebase-merged
--delete-branch-on-mergeOptionalboolean (--delete-branch-on-merge / --no-delete-branch-on-merge)
Delete the source branch when a pull request is merged
--default-workflow-permissionsOptionalenum
What a workflow job's GITHUB_TOKEN may do when its file sets no `permissions:`: restricted (contents and packages read; new repositories) or permissive (read and write)
One of:
restricted,permissive
Example
dcloud git repositories update repoIdGenerated from the API description, the same one the API checks requests against and the CLI is built from.