-
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 2024-05-22] [TS Migration] Adjust guidelines, both TS and JS markdown files #39118
Comments
On hold |
I'm Fábio from Callstack, an expert agency, and I’d like to work on this issue! |
Assigned, what are the next steps here? |
@mountiny I'm still focused on other TS / Wave stuff, let's wait this one a little more. |
I'm Julian from Callstack, an expert agency, and I’d like to work on this issue! |
The PR is ready for review! |
Triggered auto assignment to @alexpensify ( |
This was merged |
Thank you, @mountiny, for the update! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 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 2024-05-22. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Triggered auto assignment to @laurenreidexpensify ( |
Heads up, I will be offline until Tuesday, May 28, 2024, and will not actively watch over this GitHub during that period.@laurenreidexpensify - While I'm offline, I need help here completing the payment process after this one clears the 7-day period on 2024-05-22. Thanks! |
Payment summary:
|
This can be closed now I believe, thanks for help! |
Thanks, @laurenreidexpensify, for your help here! |
Follow up issue for TS migration project. Coming from this spreadsheet
cc @blazejkustra @fabioh8010
Issue Owner
Current Issue Owner: @laurenreidexpensifyThe text was updated successfully, but these errors were encountered: