Dear MetaMask team,
Reaching out to you to kindly ask for help to review our PR on GitHub - we have the wrong logo associated with our custom Fuse network on MetaMask extension and we kindly ask for your help to update it as soon as possible. We created a PR to pull the right network logo but it has 2 pending reviews from the code owner: Update Fuse logo by LiorAgnin · Pull Request #23325 · MetaMask/metamask-extension · GitHub
Please help us get the reviews done to merge the PR, thank you in advance.
Best regards,
I will raise with the team
2 Likes
@nakedwinnie hi! Could you kindly bump the team on this once again - we have added all the requirements to a new PR, missing reviews from your side.
Thank you in advance!
MetaMask:develop ← fuseio:fix/update_fuse_logo
opened 05:32PM - 14 Mar 24 UTC
## **Description**
This PR updates the Fuse mainnet logo. The motivation behi… nd this change is to ensure that the Fuse network's branding is accurately represented in MetaMask, providing users with a more reliable and visually consistent experience across the platform. The previous logo used in the wallet was outdated, and this update brings the visual in line with the current branding guidelines of the Fuse network. This improvement enhances the user interface by aligning the network's visual representation with its most current branding, ensuring that users can easily recognize and associate the Fuse mainnet within MetaMask.
[](https://codespaces.new/MetaMask/metamask-extension/pull/PR?quickstart=1)
## **Related issues**
Fixes:
## **Manual testing steps**
1. Navigate to the MetaMask extension and select the network dropdown.
2. Choose the Fuse mainnet from the list of available networks.
3. Observe the updated Fuse logo, confirming it matches the current branding guidelines provided by the Fuse network.
## **Screenshots/Recordings**
### **Before**
### **After**
## **Pre-merge author checklist**
- [x] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've clearly explained what problem this PR is solving and how it is solved.
- [x] I've linked related issues
- [x] I've included manual testing steps
- [x] I've included screenshots/recordings if applicable
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable
- [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors.
- [x] I’ve properly set the pull request status:
- [ ] In case it's not yet "ready for review", I've set it to "draft".
- [ ] In case it's "ready for review", I've changed it from "draft" to "non-draft".
## **Pre-merge reviewer checklist**
- [x] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
- [x] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
system
April 12, 2024, 1:16pm
5
This topic was automatically closed after 30 days. New replies are no longer allowed.
