Bug Submission Notice

When a fix: pull request is ready for review, Wizard posts a bug report checklist on the PR. Use it to attribute the commit (and author) that introduced the bug.

Triggering the notice

Steps:

1. Ensure the PR title starts with fix: (optionally with a scope like fix(ui):).
2. Mark the PR as Ready for review (not Draft).

Result:

• A bug submission notice appears shortly after.

Notes:

• Draft PRs do not trigger notices.

Submitting a bug report

Comment on the PR:

@holdex bug commit <commit-url> && bug author @<username>

Example:

@holdex bug commit https://github.com/holdex/my-repo/commit/1234567890 && bug author @johndoe

• Use git blame to find the commit that introduced the bug.
• <commit-url> must be a valid GitHub commit link (for example https://github.com/<org>/<repo>/commit/<sha>).

Changing a report (before merge)

Only the topmost bug report comment on the PR is recognized.

To change the commit or author while the PR is still open:

• Edit the topmost bug report comment, or
• Delete it and post a new one.

A second bug report comment is rejected until the existing topmost one is edited or deleted.

Correcting a report (after merge)

After the PR is merged, editing or deleting the original report no longer works. Dispute the attribution instead:

@holdex bug dispute <commit-url> && bug author @<username>

See Commands — Fix Pr Dispute.