From dc45ff27430d7d6dc1e365cb5843f80f1b568a95 Mon Sep 17 00:00:00 2001 From: allgandaf Date: Sat, 4 Apr 2026 20:01:12 +0530 Subject: [PATCH] Update BZ checklist to require comments on both PR and issue --- contributingGuides/BUGZERO_CHECKLIST.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/contributingGuides/BUGZERO_CHECKLIST.md b/contributingGuides/BUGZERO_CHECKLIST.md index 488d68c1cc315..de3ff5195c6f4 100644 --- a/contributingGuides/BUGZERO_CHECKLIST.md +++ b/contributingGuides/BUGZERO_CHECKLIST.md @@ -1,8 +1,9 @@ # BugZero Checklist: -- [ ] **[Contributor]** The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. +- [ ] **[Contributor]** The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. - Link to comment: + Link to the comment on the PR: + Link to the comment on the Issue: - [ ] **[Contributor]** If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in [#expensify-open-source](https://app.slack.com/client/E047TPA624F/C01GTK53T8Q) has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.