merge_pull_request_by_squash
async
¶
merge_pull_request_by_squash(
pull_request_id: PullRequestId,
repository_name: RepositoryName,
*,
config_overrides: Optional[AsyncCodeCommitClientConfig] = None,
source_commit_id: Optional[ObjectId] = None,
conflict_detail_level: Optional[ConflictDetailLevelTypeEnum] = None,
conflict_resolution_strategy: Optional[ConflictResolutionStrategyTypeEnum] = None,
commit_message: Optional[Message] = None,
author_name: Optional[Name] = None,
email: Optional[Email] = None,
keep_empty_folders: Optional[KeepEmptyFolders] = None,
conflict_resolution: Optional[ConflictResolution] = None,
) -> MergePullRequestBySquashOutput
Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the squash merge strategy. If the merge is successful, it closes the pull request.
Parameters:
-
pull_request_id(PullRequestId) –The system-generated ID of the pull request. To get this ID, use ListPullRequests.
-
repository_name(RepositoryName) –The name of the repository where the pull request was created.
-
source_commit_id(Optional[ObjectId], default:None) –The full commit ID of the original or updated commit in the pull request source branch. Pass this value if you want an exception thrown if the current commit ID of the tip of the source branch does not match this commit ID.
-
conflict_detail_level(Optional[ConflictDetailLevelTypeEnum], default:None) –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.
-
conflict_resolution_strategy(Optional[ConflictResolutionStrategyTypeEnum], default:None) –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.
-
commit_message(Optional[Message], default:None) –The commit message to include in the commit information for the merge.
-
author_name(Optional[Name], default:None) –The name of the author who created the commit. This information is used as both the author and committer for the commit.
-
email(Optional[Email], default:None) –The email address of the person merging the branches. This information is used in the commit information for the merge.
-
keep_empty_folders(Optional[KeepEmptyFolders], default:None) –If the commit contains deletions, whether to keep a folder or folder structure if the changes leave the folders empty. If true, a .gitkeep file is created for empty folders. The default is false.
-
conflict_resolution(Optional[ConflictResolution], default:None) –If AUTOMERGE is the conflict resolution strategy, a list of inputs to use when resolving conflicts during a merge.
Raises:
-
CommitMessageLengthExceededException–The commit message is too long. Provide a shorter string.
-
ConcurrentReferenceUpdateException–The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
-
EncryptionIntegrityChecksFailedException–An encryption integrity check failed.
-
EncryptionKeyAccessDeniedException–An encryption key could not be accessed.
-
EncryptionKeyDisabledException–The encryption key is disabled.
-
EncryptionKeyNotFoundException–No encryption key was found.
-
EncryptionKeyUnavailableException–The encryption key is not available.
-
FileContentSizeLimitExceededException–The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
-
FolderContentSizeLimitExceededException–The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
-
InvalidCommitIdException–The specified commit ID is not valid.
-
InvalidConflictDetailLevelException–The specified conflict detail level is not valid.
-
InvalidConflictResolutionException–The specified conflict resolution list is not valid.
-
InvalidConflictResolutionStrategyException–The specified conflict resolution strategy is not valid.
-
InvalidEmailException–The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
-
InvalidFileModeException–The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
-
InvalidPathException–The specified path is not valid.
-
InvalidPullRequestIdException–The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
-
InvalidReplacementContentException–Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
-
InvalidReplacementTypeException–Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
-
InvalidRepositoryNameException–A specified repository name is not valid.
This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.
-
ManualMergeRequiredException–The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
-
MaximumConflictResolutionEntriesExceededException–The number of allowed conflict resolution entries was exceeded.
-
MaximumFileContentToLoadExceededException–The number of files to load exceeds the allowed limit.
-
MaximumItemsToCompareExceededException–The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
-
MultipleConflictResolutionEntriesException–More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
-
NameLengthExceededException–The user name is not valid because it has exceeded the character limit for author names.
-
PathRequiredException–The folderPath for a location cannot be null.
-
PullRequestAlreadyClosedException–The pull request status cannot be updated because it is already closed.
-
PullRequestApprovalRulesNotSatisfiedException–The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
-
PullRequestDoesNotExistException–The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
-
PullRequestIdRequiredException–A pull request ID is required, but none was provided.
-
ReplacementContentRequiredException–USE_NEW_CONTENT was specified, but no replacement content has been provided.
-
ReplacementTypeRequiredException–A replacement type is required.
-
RepositoryDoesNotExistException–The specified repository does not exist.
-
RepositoryNameRequiredException–A repository name is required, but was not specified.
-
RepositoryNotAssociatedWithPullRequestException–The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
-
TipOfSourceReferenceIsDifferentException–The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
-
TipsDivergenceExceededException–The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using
git diffor a diff tool. -
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_codecommit/_services/async_code_commit.py
4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 | |