When we have a stack of revisions, analyze only the last one?

Open
#2 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

No files, tests, or code entry points are named. Start by comparing the two linked Bugzilla examples and trace how a stack of revisions is analyzed; done means findings from replaced revisions are not reported when the final revision no longer contains the problem.

Written by the indexing model from the issue text.

Description

bot enhancement

This may already have been fixed, but I'm filing it anyway in case it hasn't.
I've observed this twice:

  1. https://bugzilla.mozilla.org/show_bug.cgi?id=1402498#c12
    Here the comment was pointing out a mistake in code that was removed in a later patch in the same patch series, and replaced with code that did not have the problem.

  2. https://bugzilla.mozilla.org/show_bug.cgi?id=1403444#c161
    This sounds similar but seems to have been a mistake anyway.

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.