Feature request for product/service
BugBot
Describe the request
I’m managing a large set of rules in my repository.
Some are general code guidelines, while others are critical rules designed to prevent high-impact errors.
To avoid duplication, I’ve centralized parts of the logic and referenced them via a BUTBOT.md file.
However, this creates a few challenges in practice:
- Lack of Rule Traceability
Currently, it is difficult to identify which specific repository rule triggered a given comment.
- Only rules coming from Manual / Team / Learned rules are clearly labelled.
- For repository rules, there is no clear mapping from comment → originating rule.
Impact:
When a comment is incorrect (false positive) or misses an edge case, I cannot efficiently locate and refine the responsible rule.
Request:
Add explicit traceability from each comment to the exact rule (including repo rules), e.g. rule ID / name / source.
- Rule Priority Control
From testing, rule priority appears implicit and not configurable:
- Repository rules seem to have lower priority than Team / Learned rules.
- This does not always match the desired behaviour.
Impact:
Critical repository rules may be overridden or under-enforced.
Request:
- Allow explicit priority configuration:
- Between rule sources (Repo vs Team vs Learned)
- Within repository rules themselves
- Ideally support priority levels (e.g., Critical / High / Medium / Low)
- Limited Comment Coverage
In practice, not all violations are reported:
- Only a subset of issues is commented
- This may be an intentional trade-off (e.g., reducing noise), but it is not configurable
Impact:
When reviewing large code changes, important issues may be missed.
Request:
Provide control over comment coverage, for example:
- Maximum number of comments per PR
- Ability to enforce full coverage for high-priority rules
- Option to limit or suppress lower-priority findings
- Priority-Aware Comment Strategy (Optional Enhancement)
If prioritization is supported, an ideal behaviour would be:
- Report all Critical / High issues
- Limit Medium issues (e.g., top N)
- Optionally ignore Low priority entirely
Summary
Key capabilities that would significantly improve usability:
- Rule → comment traceability
- Configurable rule priority (global + per-repo)
- Control over comment volume and coverage
- Priority-aware reporting behaviour
If any of these capabilities already exist (even partially), I’d appreciate pointers on how to configure them.
