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

Do not hardcode GitHub URLs and branch-to-repo mappings; resolve them from Phabricator

Open
#6,633 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, python
Domain
devtools, tooling

Research direction

Start by comparing the duplicated mappings and URLs in agents/build-repair/hackbot_agents/build_repair/resolve.py, agents/test-repair/hackbot_agents/test_repair/resolve.py, and agents/test-repair/hackbot_agents/test_repair/notify.py, along with each agent's hackbot.toml. Read the referenced Phabricator repository URI configuration first. Done means these values are resolved from Phabricator rather than maintained as duplicate hardcoded mappings or templates.

Written by the indexing model from the issue text.

Description

reviewhelper-api

agents/build-repair/hackbot_agents/build_repair/resolve.py and agents/test-repair/hackbot_agents/test_repair/resolve.py each independently hardcode an identical branch-to-repo-path map (autoland, mozilla-central, try, etc.) plus Taskcluster/Lando/hg URLs, and agents/test-repair/hackbot_agents/test_repair/notify.py hardcodes a GitHub commit URL template. Every agent's hackbot.toml also hardcodes repo_url.

Look these up from Phabricator's own repository configuration instead (see for example https://phabricator-dev.allizom.org/source/ff-test-autoland-dev/manage/uris/), so branch names always match what is actually configured on Phabricator rather than a second hardcoded copy.

Dominant language
Python
Stars
571
Forks
355
Avg merge
2d 2h
Merged PRs (30d)
78

Getting set up

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/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.