Add a rule/guardrail mechanism for Hackbot actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by mapping the Hackbot actions and agents that can perform try pushes and patch submissions, then identify where a shared policy layer could inspect those actions. Done means the layer can enforce the stated per-run limits and reject submissions for bugs other than the run's assigned bug.
Written by the indexing model from the issue text.
Description
Add a generic policy layer that can enforce rules across actions and agents, for example: no two try pushes in the same run, no two patch submissions in the same run, and refusing to submit a patch to a bug other than the one the run is assigned to.
- 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 ·