Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Custom specification of PR titles #186
It would be great to control the content of the PR title. I know labels is probably a better approach but we have some pipeline steps that look at strings in the title to determine if it should build a test deployment. Would be useful to always build test deployments for depdendabot PRs.
Thanks for the request @dwaynebailey.
We've been cautious about this one because Dependabot's PR title logic isn't totally trivial - you can see the code here. As a result, full customisation could be quite complicated for users.
Do you have access to anything else in your pipeline steps? Labels are an obvious one, but Dependabot also creates all of its PRs using the @dependabot-bot account, signs-off the commit messages, prefixes its branches with
This would be really nice to have this kind of feature.
For my own case, I'm maintaining an app (a CLI tool for our projects at work, used for building JS/CSS assets) by updating dependencies through Dependabot pull requests. I consider those dependencies as features because this CLI tool wraps Rollup, Bublé, ESLint, Gulp, images minification [...].
I'm using semantic-release for automatic releases, but sometimes it doesn't release anything because every commits (squashed dependabot pull requests) between master and the last version is a
To force a new release when I only updated dependencies, I have to rename commit message
EDIT: Well, I think I can configure standard-version plugin commit-analyzer to makes