microsoft / microsoft/agent-governance-toolkit

Validate PR title fails on every recreated dependabot PR (capitalized Bump/Update)

Open
#3,559 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
6.3k
Forks
1.1k
Avg merge
5d 11h
Merged PRs (30d)
142

Description

Every PR in the recreated dependabot batch (#3541–#3554, generated under the restructured .github/dependabot.yml) failed the Validate PR title check because dependabot now emits chore(deps): Bump ... / chore(deps): Update ... with a capitalized verb, while the title validator requires a lowercase subject after the type prefix. The same happened to #3386/#3392 after their recreation. Each PR had to be manually retitled to lowercase before it could merge — pure babysitting.

Options, in order of preference:

  1. Relax the title validator to accept a capitalized first word for app/dependabot-authored PRs (or case-insensitively match the subject in general — conventional-commits tooling generally treats the description as free text).
  2. Keep the strict rule and have a small workflow auto-retitle dependabot PRs (chore(deps): Bumpchore(deps): bump) on pull_request_target: opened.

Either removes a manual step from every future dependabot batch. The check name is Validate PR title; dependabot's verb capitalization is not configurable via commit-message settings, so this has to be handled on our side.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the workflow or configuration for the Validate PR title check and inspect the recreated Dependabot setup in .github/dependabot.yml. Compare the titles from PRs #3541–#3554 and verify that future capitalized Dependabot verbs pass validation or are automatically retitled without manual intervention.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.