### Issue 1
.mergify.yml:8-9
PRs targeting `main` with valid titles such as `feat!: remove the old API` or `fix(api)!: change error responses` fail this check. The regex requires `:` immediately after the type or scope, even though the release policy explicitly supports `feat!` for major releases. Contributors must remove the marker or remain blocked from merging. Allow an optional `!` before `:`.
```suggestion
^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\\(.+\
\\))?!?:"
```
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
### Issue 2
.mergify.yml:9
The regex ends at `:`, so both `fix:` and `fix:no space` satisfy the check. Contributors get a passing result even though these titles lack the required space or description. Require a space followed by a nonblank description so the check enforces the format it promises.
```suggestion
\\))?: \\S.*"
```
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Summary
Adds a Mergify protection that checks PR titles targeting main.
Mergify checks titles on pull requests targeting main.