Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateUnreferencedMergeCommitInput

import type { CreateUnreferencedMergeCommitInput } from "https://aws-api.deno.dev/v0.3/services/codecommit.ts?docs=full";
interface CreateUnreferencedMergeCommitInput {
authorName?: string | null;
commitMessage?: string | null;
conflictDetailLevel?: ConflictDetailLevelTypeEnum | null;
conflictResolution?: ConflictResolution | null;
conflictResolutionStrategy?: ConflictResolutionStrategyTypeEnum | null;
destinationCommitSpecifier: string;
email?: string | null;
keepEmptyFolders?: boolean | null;
mergeOption: MergeOptionTypeEnum;
repositoryName: string;
sourceCommitSpecifier: string;
}

§Properties

§
authorName?: string | null
[src]

The name of the author who created the unreferenced commit. This information is used as both the author and committer for the commit.

§
commitMessage?: string | null
[src]

The commit message for the unreferenced commit.

§
conflictDetailLevel?: ConflictDetailLevelTypeEnum | null
[src]

The level of conflict detail to use. If unspecified, the default FILE_LEVEL is used, which returns a not-mergeable result if the same file has differences in both branches. If LINE_LEVEL is specified, a conflict is considered not mergeable if the same file in both branches has differences on the same line.

§
conflictResolution?: ConflictResolution | null
[src]

If AUTOMERGE is the conflict resolution strategy, a list of inputs to use when resolving conflicts during a merge.

§
conflictResolutionStrategy?: ConflictResolutionStrategyTypeEnum | null
[src]

Specifies which branch to use when resolving conflicts, or whether to attempt automatically merging two versions of a file. The default is NONE, which requires any conflicts to be resolved manually before the merge operation is successful.

§
destinationCommitSpecifier: string
[src]

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).

§
email?: string | null
[src]

The email address for the person who created the unreferenced commit.

§
keepEmptyFolders?: boolean | null
[src]

If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If this is specified as true, a .gitkeep file is created for empty folders. The default is false.

§

The merge option or strategy you want to use to merge the code.

§
repositoryName: string
[src]

The name of the repository where you want to create the unreferenced merge commit.

§
sourceCommitSpecifier: string
[src]

The branch, tag, HEAD, or other fully qualified reference used to identify a commit (for example, a branch name or a full commit ID).