| CodePipeline | Notes |
---|
Branch name | Status |
---|
colour | Purple |
---|
title | in the works |
---|
|
| The CodePipeline events readily include the branch name so we can provide this capability soon.
|
Commit message … | | |
… of last pushed commit | Status |
---|
colour | Green |
---|
title | supported |
---|
|
| |
… of all pushed commits | Status |
---|
colour | Yellow |
---|
title | unsupported |
---|
|
| The CodePipeline events only include the last commit ID, so if a push contains multiple commits, we lack access to the resp. commit data – we are investigating how to eventually work around this via a CodeBuild action that uses a full clone to extract and forward this data.
|
Pull request title … | | |
… before merge | Status |
---|
colour | Red |
---|
title | unsupported |
---|
|
| We do not have access to pull request data from the various upstream Git providers, so this seems blocked for now.
|
… after merge | Status |
---|
colour | Blue |
---|
title | conditional |
---|
|
| This works if your Git tooling references the issue key …
… either in the PR title and in the subsequent merge commit message (default workflow in e.g. GitHub, where the title is used in the commit message, while the PR ‘description’ aka first comment is ignored) … or alternatively in the PR description and in the subsequent merge commit message (default workflow in e.g. Bitbucket, where the description is used in the commit message, while the PR title is ignored)
|