You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-13] Payment issue for E/App PR#105696 #106185
@Eskalifer1 The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
[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.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Important distinction: Removing the GBR from paid invoices was intentional. The leftover dead code—not a new user-facing regression—is what the cleanup PR addressed.
Activity
melvin-bot commentedon Nov 6, 2026
@Eskalifer1 The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Nov 9, 2026
@Eskalifer1 Whoops! This issue is 2 days overdue. Let's get this updated quick!
Eskalifer1 commentedon Nov 12, 2026
@MelvinBot find offending PR
Eskalifer1 commentedon Nov 12, 2026
Contributor+ Checklist:
[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 the comment on the PR: https://github.com/Expensify/App/pull/53802/changes#r4550073737
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
N/A - dead code removal
MelvinBot commentedon Nov 12, 2026
The PR that made this code unreachable was Fix: Remove GBR and 'Add a bank account' for paid invoices, merged December 19, 2024.
!isSettled(...)at both call sites, making both branches impossible.Important distinction: Removing the GBR from paid invoices was intentional. The leftover dead code—not a new user-facing regression—is what the cleanup PR addressed.
view run
melvin-bot commentedon Nov 12, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Nov 12, 2026
Payment Summary
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Nov 16, 2026
Claude posting on behalf of Matt:
Ready. Job price: $175 (standard, no Help Wanted, first review 2026-11-04).
The C+ checklist says "N/A - dead code removal": no test steps for Caps+Y.
Melvin's summary says Eskalifer1 needs a manual offer.
Next: pay.
Evidence
PAYPREP v1Eskalifer1 commentedon Nov 16, 2026
Note: This issue shold be paid via Upwork yet