Uses of Class
com.atlassian.bitbucket.scm.git.command.merge.conflict.AbstractGitMergeConflict

Packages that use AbstractGitMergeConflict

Package	Description
com.atlassian.bitbucket.scm.git.command.merge.conflict

Uses of AbstractGitMergeConflict in com.atlassian.bitbucket.scm.git.command.merge.conflict

Subclasses of AbstractGitMergeConflict in com.atlassian.bitbucket.scm.git.command.merge.conflict

Modifier and Type	Class	Description
class	AbstractPathGitMergeConflict
class	AddAddGitMergeConflict
class	AddRenameGitMergeConflict
class	ContentGitMergeConflict
class	ConvergentDirectoryRenameGitMergeConflict	Indicates an implicit directory rename failed because multiple directories which each contained a subset of the same files were renamed to the same target directory.
class	ConvergentRenameGitMergeConflict	Describes a conflict where two different files are renamed to the same destination.
class	DeleteModifyGitMergeConflict
class	DeleteRenameGitMergeConflict
class	DirectoryFileGitMergeConflict
class	DivergentDirectoryRenameGitMergeConflict	Indicates a directory rename failed because a single directory was renamed to multiple target directories and git merge could not decide where to move a file.
class	DivergentRenameGitMergeConflict	A merge conflict where the same file or directory has been renamed differently on each side of a merge.
class	FileDirectoryGitMergeConflict
class	ImplicitDirectoryRenameGitMergeConflict	Indicates an implicit directory rename failed because an existing directory or file prevented git merge from moving one or more files to the renamed directory.
class	MergedRenameGitMergeConflict	Describes a conflict where two different files are renamed to the same destination.
class	ModifyDeleteGitMergeConflict
class	RenameAddGitMergeConflict
class	RenameDeleteGitMergeConflict
class	SubmoduleGitMergeConflict	A merge conflict where the same submodule has been updated to point to different commits.
class	UnknownGitMergeConflict