-
Notifications
You must be signed in to change notification settings - Fork 1
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
[feature request] renaming of automatically-made dep update prs #184
Comments
When we do make our package releases, our deployments should contain a @snyk-bot
@dependabot
@renovate-bot |
Renovate bumping a GitHub action: #196 How should we standardize these PR title renamings? |
This is going to have to be taken care of by @shellscape. |
So, what is a "Semantic PR" then? We're removing the app and will be defining the term here. FTR: https://github.com/Ezard/semantic-prs being non-configurable means that it is now removed as it was unable to be used. Would prefer using https://github.com/OpenINF/openinf-action-semantic-pull-request |
It would at least be composed of:
|
@shellscape communicated to me that his time is too limited to commit to getting this worked out, so went ahead and unassigned, but hopefully he will be pinged on this to review our solution when ready. |
Renovate now concludes PR titles w/ major (breakingly) changed updated deps w/ But not always; perhaps only for the monorepos. |
Seems like the PR for bumping an action is going to have to be made by @OpenINFbot w/ proper automation code seeing as how Renovate is currently quite bad at naming the actual version being updated in the PR title. See: OpenINF/docker-fisher#19 |
Refs: #664 that would ideally be built here, actually, via ci per pr. |
We have regularly been receiving dependency update requests from the following:
@snyk-bot
@dependabot
@renovate-bot
They each have their own way of titling their PRs and sometimes those titles match the first line of the commit message (other times they do not). The request is to fix these requests to match our needs.
The text was updated successfully, but these errors were encountered: