-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: Normalize transaction controller patch #7213
Conversation
Moving into draft because it conflicts with #7209 which is more urgent. After that is merged, I can update the patch and mark this as ready for review |
fac41eb
to
254eb7c
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #7213 +/- ##
=======================================
Coverage 33.02% 33.02%
=======================================
Files 1004 1004
Lines 26888 26888
Branches 2131 2131
=======================================
Hits 8881 8881
- Misses 17571 17573 +2
+ Partials 436 434 -2 ☔ View full report in Codecov by Sentry. |
e910c17
to
f66f215
Compare
Passing E2E smoke tests on iOS: https://app.bitrise.io/build/b5bf427a-a45c-4f21-85bc-c03659cd4cc7 (android is currently not passing on |
The patch has been updated here also: #7035 (comment) |
a432377
to
c72b85f
Compare
This has been rebased, and updated with the changes from #7226 (which added a script to automate transaction controller patch updates, and improved the patch instructions) |
The transaction controller patch has been re-generated following a set of steps that has been documented in the patch itself. This resolves inconsistencies present in the patch resulting from different workflows being used to update it. This includes no functional changes.
The process for updating the transaction controller patch has been automated with the `patch:tx` script. This script follows the same steps I had used, except that the patch comment is now in a separate file and the instructions have been improved.
c72b85f
to
501e7d0
Compare
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Development & PR Process
release-xx
label to identify the PR slated for a upcoming release (will be used in release discussion)needs-dev-review
label when work is completedneeds-qa
: PR requires manual QA.No QA/E2E only
: PR does not require any manual QA effort. Prior to merging, ensure that you have successful end-to-end test runs in Bitrise.Spot check on release build
: PR does not require feature QA but needs non-automated verification. In the description section, provide test scenarios. Add screenshots, and or recordings of what was tested.QA Passed
label when QA has signed off (Only required if the PR was labeled withneeds-qa
)team-
(orexternal-contributor
label if your not a MetaMask employee)Description
The transaction controller patch has been re-generated following a set of steps that has been documented in the patch itself. This resolves inconsistencies present in the patch resulting from different workflows being used to update it. This includes no functional changes.
Issue
This relates to https://github.com/MetaMask/mobile-planning/issues/1226 (this makes it possible to minimize the diff for the patch changes needed as part of the next controller upgrades)
Checklist