Skip to main content

merge_pull_request

Facts​

DescriptionMerge pull request
SchemaConnectors.Bitbucket.functions.MergePullRequest
ServiceBitbucket

Input parameters​

Required input parameters

bitbucket_access_tokenslack#/types/credential/oauth2Required

bitbucket access token. See the authentication section for details.

pull_request_idstringRequired

The ID of the pull request you wish to merge

Examples
ABC123-changeme
repo_slugstringRequired

The ID of the repository containing the pull request you wish to merge

Examples
DEF54321-changeme
workspacestringRequired

The ID of the workspace containing the repository where the pull request can be found

Examples
ABC12345-changeme

Optional input parameters

close_source_branchbooleanOptional

If true, the source branch will be closed once the merge is complete

merge_strategystringOptional

The merge strategy to use

Accepted values
merge_commitsquashfast_forward
messagestringOptional

A message added to the pull request merge action

Output parameters​

Optional output parameters

pull_request_idstringOptional

Pull request ID

repo_slugstringOptional

Repository ID

responsestringOptional

Response code

workspacestringOptional

Bitbucket workspace ID

Authentication​

End-user authentication

User workflows that include a connector function relying on end-user authentication can only be started with a link trigger.

{
"bitbucket_access_token": {
"credential_source": "END_USER"
}
}

End-user experience: User will be prompted to link their external account via OAuth when they first start the workflow that contains this connector.

Developer experience: Developer does not have to implement authentication in the app.

Usage info​

First, import Connectors from deno-slack-hub into your project's import_map.json file, like this:

import_map.json
{
"imports": {
"deno-slack-hub/": "https://deno.land/x/deno_slack_hub@2.2.0/",
"deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.14.2/",
"deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/"
}
}

Next, import Connectors at the top of your workflow's definition file:

my_workflow_file.ts
import { Connectors } from "deno-slack-hub/mod.ts";

Finally, add the connector as a step in your workflow just like you would a Slack function.

my_workflow_file.ts
SomeWorkflow.addStep(
Connectors.Bitbucket.functions.MergePullRequest, {
//...

🧙🏼 Your admin may need to approve the connector first. If your workspace has been configured to only allow admin-approved apps, the CLI will prompt you to send an admin approval request the first time you try to use a connector that hasn't been approved by an admin yet. While waiting for admin approval, the CLI may report an error like this:

Workflow function X is referring to an unknown step output parameter Y

You can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.