-
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
[HOLD for payment 2025-01-28] Create Expense Part 2 - Clean up #54006
Comments
Hi, I'm Julian from Callstack - expert agency - and I would like to work on this issue. |
I started working on this issue today, PR should be ready early next week. |
I've made some progress on it today, I might be able to publish a PR tomorrow. |
The PR is ready for review! |
I'm still waiting for the PR to be reviewed |
PR is waiting for final review |
The PR is waiting to be reviewed and merged. |
Update: The PR was approved by @mananjadhav and is now waiting for @grgia 's green light to merge it in its current form |
Update: Some more changes were requested by @grgia, there is also some minor merge conflict. I will be addressing both tomorrow. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Update: @grgia requested one more change on the PR, I am going to work on it tomorrow. |
@JKobrynski any updates on the small change requested by @grgia ? |
Update: PR was updated with fixes to related issues. It's waiting for another round of review! |
Reviewed and left a few test cases to cover |
Update: All reported issues have been fixed. There were also some related eslint problems, I fixed them too. |
Update: I updated the PR, fixed conflicts and lint errors. It was merged. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.87-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-01-28. 🎊 For reference, here are some details about the assignees on this issue:
|
Triggered auto assignment to @dylanexpensify ( |
Assigning BZ for @mananjadhav payment @dylanexpensify |
Nice one! Paying tomorrow! |
Payment summary: Contributor+: @mananjadhav $250 via NewDot Please apply/request! |
@grgia @dylanexpensify I was wondering if we could bump the payout for this particular PR a bit. This required more effort in testing than I expected and went through several iterations. |
Payment Summary
BugZero Checklist (@dylanexpensify)
|
@grgia @dylanexpensify In case you missed my previous comment |
Payment summary: Contributor+: @mananjadhav $500 via NewDot Please apply/request! |
Thanks @dylanexpensify and @grgia. Appreciate it. |
$500 approved for @mananjadhav |
Part 2 of #53656
Issue for cleaning up references to the old flow/beta flag.
@JKobrynski
The text was updated successfully, but these errors were encountered: