Dependabot doesn't use the `chore` type on my repositories; it uses `build`
See original GitHub issueI was trying to figure out why commitlint-github-action was giving me errors for body-max-line-length
Turns out we’re just checking for the chore
type in commitlint.config.js
const isDepsCommit = type === 'chore' && (scope === 'deps' || scope === 'deps-dev')
My dependabot is giving me build
type instead of chore
with default configs
version: 2
updates:
- package-ecosystem: "npm"
directory: "/frontend"
schedule:
interval: "monthly"
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
Wrong type when using the Conventional Commits ... - GitHub
I use build(deps-dev): for non production (i.e. development dependencies) such as build tools and linters. These do not trigger a new release. I ......
Read more >Setting up Dependabot with GitHub actions to approve and ...
First, go to your repository Settings tab and under the Options section, ensure that Allow auto-merge is checked. This does not make every...
Read more >Keep all your packages up to date with Dependabot
Here are some tips to more efficiently prioritize and take action on your alerts, so you can get back to building.
Read more >Yarn lock: how it works and what you risk without maintaining ...
Yarn uses that information to check if it needs to update anything – it compares dependency versions currently installed in a project (listed...
Read more >Auto updating dependencies in GitHub - Medium
Using Dependabot and GitHub actions it's possible to automate your entire dependency upgrade process. Learn how to update Laravel upon new releases.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
AFIK that information is not available. In (https://github.com/wagoid/commitlint-github-action/issues/233#issuecomment-921541952) we also got that question. That information being not available is not decided on by this action, but rather something from commitlint, or I even believe the Git hook, itself. So should be in upstream commitlint (see https://github.com/conventional-changelog/commitlint/issues/2455 and https://github.com/conventional-changelog/commitlint/issues/321 for example). Hope this helps.
That is really something that you should just change in your repositories’ commitlint configuration, and make sure this uses your configuration file.