-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payment issue for E/App PR#33253 #33409
Comments
Triggered auto assignment to @dylanexpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~0147bb0a7b2d6c2f4d |
Bug0 Triage Checklist (Main S/O)
|
Current assignee @cubuspl42 is eligible for the Internal assigner, not assigning anyone new. |
pending merge and no regressions |
@cubuspl42, @dylanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@cubuspl42, @dylanexpensify Eep! 4 days overdue now. Issues have feelings too... |
@cubuspl42, @dylanexpensify Huh... This is 4 days overdue. Who can take care of this? |
@cubuspl42 please apply! |
@cubuspl42 @dylanexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Made public @cubuspl42!! |
Applied |
@cubuspl42 @dylanexpensify this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
@cubuspl42, @dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
offer sent! |
Accepted |
done |
Issue created to compensate the Contributor+ member for their work on #33253
E/E issue linked to the PR - https://github.com/Expensify/Expensify/issues/316104.
Contributor+ member who reviewed the PR - @cubuspl42.
Wait 7 days after the PR is deployed to production before issuing payment in case there are regressions.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: