-
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 2024-06-20] [HOLD for payment 2024-06-18] [Details Revamp] Remove DetailsPage.tsx #42079
Comments
Triggered auto assignment to @anmurali ( |
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
Hey, I'm from SWM and I will work on this. |
@kosmydel will this one effectively come last with the changes, or are we waiting on something else? |
We are currently waiting for the PRs at #42188 and #41972 to be merged. I don't want to open this PR yet because there might be changes during the review process of the above PRs that could impact the review process of this one (as this PR is based on the above ones). |
Nice, so #42188 to go! |
This one is waiting for #42188, but I opened it for review anyway to speed up the process a bit (I've notified the C+ that it is not based on the main branch). |
We can take this issue off hold as the blocking PR was merged :) |
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. |
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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.82-4 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-06-20. 🎊 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:
|
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@kosmydel - can you propose regression test steps? |
Hey @anmurali, I've never done something like this, but here you are:
|
@shawnborton, @anmurali, @grgia, @kosmydel Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Great work on these @kosmydel ! I made some minor tweaks, could you confirm my changes?
|
Looks great @grgia! |
Not overdue! Working out final details but we have this live in product. |
@anmurali I think we've got everything we need to close this one out |
@shawnborton, @anmurali, @grgia, @kosmydel Eep! 4 days overdue now. Issues have feelings too... |
@shawnborton, @anmurali, @grgia, @kosmydel 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@shawnborton, @anmurali, @grgia, @kosmydel 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@anmurali friendly bump |
No payments needed. Regression test added. |
https://docs.google.com/document/d/1-xSZdSZZIuIl0fPO7yypkKfcbWEsnNFAs50ptgL3Gnw/edit#bookmark=id.azg8eofhvuhz
Issue Owner
Current Issue Owner: @anmuraliThe text was updated successfully, but these errors were encountered: