Skip to main content

AssetMergeManualPreview

No description

type AssetMergeManualPreview {
  errors: [String!]!
  hasIntegrationConflict: Boolean!
  newBranches: [AssetMergeNewBranch!]!
  targetRepositoryAsset: Asset
}

Fields​

AssetMergeManualPreview.errors ● [String!]! non-null scalar​

Why the selection is invalid (empty = a valid merge).

AssetMergeManualPreview.hasIntegrationConflict ● Boolean! non-null scalar​

True when the selected assets have diverging defect-tracker configs on a shared integration — the merge keeps one and repoints the rest, so a Super User must review it. (Scanners never conflict: they dedup deterministically, most-recent wins.)

AssetMergeManualPreview.newBranches ● [AssetMergeNewBranch!]! non-null object​

The incoming assets and the branch name suggested for each (seeds the map-branches step).

AssetMergeManualPreview.targetRepositoryAsset ● Asset object​

The existing repository the selection merges INTO (only for merge-into-existing); null for a fresh merge. Query id/name/repoUrl/branches to show what it already has. It is also the asset that SURVIVES the merge — on a fresh merge nothing here names the survivor, which the isDefault choice on mergeRepository decides.

Returned By​

assetMergeManualPreview query

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.