New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom specification of PR titles #186

Open
dwaynebailey opened this Issue Sep 17, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@dwaynebailey

dwaynebailey commented Sep 17, 2018

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.

@greysteil

This comment has been minimized.

Member

greysteil commented Sep 18, 2018

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 dependabot/ and includes a Dependabot commands and options section in the PR message. Could you use any of those to identify Dependabot PRs?

@dwaynebailey

This comment has been minimized.

dwaynebailey commented Sep 18, 2018

@greysteil the most likely candidate I started to explore is indeed labels and I'll look at that. Currently users prefix PRs with [PREVIEW] if they need a preview build. They could potentially do the same with labels, if I can change the pipeline.

@Kocal

This comment has been minimized.

Kocal commented Nov 6, 2018

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 chore commit.

To force a new release when I only updated dependencies, I have to rename commit message chore(deps): ... to feat(deps): ..., but this is not really ideal. 😕

Something like @dependabot use git-commit-type <type> - or through UI - would be great! 😄

Thanks you


EDIT: Well, I think I can configure standard-version plugin commit-analyzer to makes chore(deps): ... commits be associated as a patch release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment