.pmbot.yml
Pmbot configuration file
| Type | object |
|---|---|
| File match |
.pmbot.yml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/pmbot-yml/latest.json |
| Source | https://raw.githubusercontent.com/pmbot-io/config/master/pmbot.yml.schema.json |
Validate with Lintel
npx @lintel/lintel check
Properties
Definitions
Update slug. For example, "npm", or, "npm-0" when there are multiple pmUpdates with packageManager npm.
Whether to squash commits of the update branch
Whether to remove the update branch
Update slug. For example, "npm", or, "npm-0" when there are multiple pmUpdates with packageManager npm.
Package manager update status
A status emoji corresponding to the package manager update status
An authentication token. For Gitlab, this should be a personal access token. For Github, it should be a Github personal access token.
Issue title
This handlebars template is passed the following context:
{
"slug": "myPm",
"status": "myStatus",
"statusEmoji": "✅"
}
Additional text to embed in the issue description
Usernames to assign to the issue created. Note that Gitlab CE only allows one assignee.
[]
Close open issues that were created by Pmbot. This option prevents multiple issues open simultaneously when you don't have the time to look at them.
An authentication token. For Gitlab, this should be a personal access token. For Github, it should be a Github personal access token.
Merge request title
This handlebars template is passed the following context:
{
"slug": "myPm",
"status": "myStatus",
"statusEmoji": "✅"
}
Additional text to embed in the merge request description
Usernames to assign to the issue created. Note that Gitlab CE only allows one assignee.
[]
Close open merge requests that were created by Pmbot. This option prevents multiple merge requests open simultaneously when you don't have the time to merge them.
[GITLAB only] Whether commits of the merge request source branch should be squashed
[GITLAB only] Whether the merge request source branch should be deleted
[GITHUB only] Whether maintainers can modify the created pull request
Sender's email. Be aware that some providers (e.g. OBVH) will silently ignore sending the email when the sender address does not match the username.
Recipient address(es)
Email subject
This handlebars template is passed the following context:
{
"slug": "myPm",
"status": "myStatus",
"statusEmoji": "✅"
}
Nodemailer transport options
3 nested properties
Sender's email. Be aware that some providers (e.g. OBVH) will silently ignore sending the email when the sender address does not match the username.
Recipient address(es)
Email subject
This handlebars template is passed the following context:
{
"slug": "myPm",
"status": "myStatus",
"statusEmoji": "✅"
}
Additional text to embed in the email body
Channels where to send the message. Obsolete parameter when you have enabled Lock to this channel for the incoming webhook.
Message title
This handlebars template is passed the following context:
{
"slug": "myPm",
"status": "myStatus",
"statusEmoji": "✅"
}
Additional text to embed in the message body
Slack webhook URL.
To get this URL:
- Create a custom Slack App. Fill in the form as follows:
- App Name:
Pmbot - Development Slack Workspace: Workspace where you want Pmbot to be integrated to
- App Name:
- Click "Create App". You are redirected to your app's page.
- Under menu section Features, select Incoming Webhooks, then toggle on Activate Incoming Webhooks. A new section named Webhook URLs for Your Workspace appears.
- Under section Webhook URLs for Your Workspace, click Add New Webhook To Workspace, then select the channel to which you want messages to be sent, for example
#pmbot. - Once added, copy the webhook URL and configure this action with it
Slack message title
This handlebars template is passed the following context:
{
"slug": "myPm",
"status": "myStatus",
"statusEmoji": "✅"
}
Additional text to embed in the slack message body
Header name
Header value
Url to call
Data that will be appended to the webhook payload in property "extraData"
Additional headers to append to the HTTP request
A Javascript regular expression.
Default rule for bumping dependencies. Used unless a specific rule is configured.
Bump rules for specific dependencies. The first rule to match is used. When no custom rule is found here, we fallback the default rule.
[]
Bump configuration. Patterns are matched against package names.
Bump configuration. Patterns are matched against dependency names formed as "
Path to a maven settings.xml file which contains credentials for private repositories.
When to trigger this action
[]
When false, all updates are made at once and we do not wait for CI feedback.
Name of the dependency
Version of the dependency before it was updated
Version of the dependency after it was updated
2 nested properties
1 nested properties
When false, all updates are made at once and we do not wait for CI feedback.
Prefix of the update branch
Commit message template
This handlebars template is passed the following context:
{
"dependency": "chalk",
"versionBefore": "1.0.0",
"versionAfter": "1.0.1"
}
List of dependencies to ignore. Each item should be a Javascript regular expression.
[]
When true, the update branch will not be deleted when the package manager update status is failure.