-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2023-10-23] [HOLD for payment 2023-10-23] [$250] Migrate RequestorOnfidoStep.js to function component #16246
Comments
I'd love to work on this. |
I can work on this! |
@neonbhai don't spam proposal on hold Gh try to find migration on unhold issues |
I can work on this issue. |
@olexyt do not spam on all issue and also this are on hold |
I am able to work on this task. |
i will work on this |
Hi! I'm Bartek from Callstack - an expert contributor group and I would like to work on this one. |
📣 @barttom! 📣
|
Contributor details |
Job added to Upwork: https://www.upwork.com/jobs/~0108c7eff871f84756 |
Triggered auto assignment to @jliexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Dibs |
This issue has not been updated in over 15 days. @barttom, @sobitneupane, @jliexpensify eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
This isn't overdue right? Also, is any payment from me needed? Sobit takes New.Dot and @barttom invoices us right? |
Hey @jliexpensify! |
No worries! Thanks for letting us know. @barttom just to confirm that you invoice us for payment, correct? |
@jliexpensify I’m a part of callstack team, so I afaik they are care of invoices 😉 |
Hi @sobitneupane @barttom just checking: this hasn't been competed/implemented right? |
@jliexpensify It has been merged |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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 2023-10-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Payment Summary (due to regression)
NO UPWORKS JOB |
@jliexpensify I wasn't assigned to the PR, and I didn't review it. Therefore, no payment is due to me. |
Fixed, thanks for letting me know! |
Class Component Migration
Filenames
React.Component
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: