schedule at least one task which failed and caused a backout when the revision gets updated with the a fix afterwards

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the task-scheduling and revision-update handling in the code-review bot, then trace how a backout is recorded. The change is done when an updated revision schedules at least one task that previously failed and caused the backout, preventing relanding with the same or newly introduced issues.

Written by the indexing model from the issue text.

Description

Prevent relanding with the same failure or other issues not fixed or new after a backout.

Schedule at least one task which failed and caused a backout when the revision gets updated with the a fix afterwards.

Dominant language
Python
Stars
67
Forks
52
Avg merge
3d 23h
Merged PRs (30d)
54

Contributor guide

Open the 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/code-review

All issues in mozilla/code-review

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.