Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[New Rule] Move regressions under Web Compatibility :: Site Report to the correct component

Open
#3,010 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

No source file or test is named. Start by locating existing BugBot rules that inspect Bugzilla components or regressions and their tests; implement the stated condition and component move, then verify behavior using the example regression and rule tests.

Written by the indexing model from the issue text.

Description

From time to time, Bugs filed under Web Compatibility :: Site Report end up being the result of a Firefox code change and become a regression with a regressed by bug identified.

BugBot should move these bugs to the correct component, using the compoent of the regressor as a good start.

See Example: https://bugzilla.mozilla.org/show_bug.cgi?id=2038512

Rule:
IF compoent == Web Compatibility :: Site Report AND regressed by!= empty THEN move to the component of the regressed by bug

Dominant language
Python
Stars
69
Forks
93
Avg merge
2d 12h
Merged PRs (30d)
22

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from mozilla/bugbot

All issues in mozilla/bugbot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.