Skip to main content

MergeRepositoryBranchInput

No description

input MergeRepositoryBranchInput {
id: ID
assetId: ID
branchName: String
isDefault: Boolean
}

Fields​

MergeRepositoryBranchInput.id ● ID scalar​

An EXISTING branch of the target repository, referenced only to mark it as the default. Omit for an incoming asset's new branch.

MergeRepositoryBranchInput.assetId ● ID scalar​

The incoming asset whose data becomes a branch. Required when id is absent.

MergeRepositoryBranchInput.branchName ● String scalar​

The branch name the incoming asset becomes. Required when id is absent.

MergeRepositoryBranchInput.isDefault ● Boolean scalar​

True if this branch becomes the repository's default branch (at most one). On an INCOMING asset it ALSO makes that asset the surviving repository: the merge keeps that asset row, so its id, name, url and criticity are the ones the repository ends up with, its AST configuration wins (another asset's is adopted only when the survivor has none), and every other selected asset is soft-deleted. repoUrl is NOT inherited — the merge overwrites it with this mutation's repositoryUrl, canonicalized. Inert on an EXISTING branch (that repository always survives). With no entry flagged, the survivor is elected from branch history.

Member Of​

MergeRepositoryInput input

Contribute to the Docs

Found something outdated or missing? Help us improve the documentation with a quick suggestion or edit.

How to contribute

Resources

By exploring our content, you'll find resources that will enhance your understanding of the importance of a Security Application Program.

Conviso Blog: Explore our blog, which offers a collection of articles and posts covering a wide range of AppSec topics. The content on the blog is primarily in English.

Conviso's YouTube Channel: Access a wealth of informative videos covering various topics related to AppSec. Please note that the content is primarily in Portuguese.