Add diff ID context to regular Phabricator comments
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
Research direction
No file or test is named. Locate the code that builds regular Phabricator comment context and compare it with the inline @hackbot comment path that already includes diff_id. Done means regular comment context also includes the relevant diff_id, with the existing related tests passing.
Written by the indexing model from the issue text.
Description
Inline @hackbot comments include their diff_id, but regular comments do not. It may also be helpful to include a diff_id in regular Phabricator comment context.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 66
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mozilla/bugbug
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good-first-bug hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
good-first-bug hackbot
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Similar issues
-
area: harness bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Human-Agent-Society/reef#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
learningequality/kolibri#15351 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Name consistency Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eellak/triplestore#65 · 1 comment ·