v1.2.9 Bug Report #198
Labels
external-contributor
Issue or PR created by user outside MetaMask organisation
INVALID-ISSUE-TEMPLATE
Issue's body doesn't match any issue template.
Comments
gauthierpetetin-test
added
external-contributor
gauthierpetetin
added a commit
to MetaMask/metamask-mobile
that referenced
this issue
Aug 30, 2024
…e anymore (#10903) ## **Description** The description of bug report issues created by this [Github action](https://github.com/MetaMask/metamask-mobile/blob/main/.github/workflows/create-bug-report.yml) wasn't up-to-date anymore. It was still referencing Zenhub which we don't use anymore. ## **Related issues** Fixes: Same PR for Extension repo: MetaMask/metamask-extension#26777 ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** See description of this [example issue](gauthierpetetin-test/repo_test#198). <img width="660" alt="Screenshot 2024-08-29 at 17 05 24" src="https://github.com/user-attachments/assets/2929ff32-b6b5-41d2-9ff0-ce65acc29620"> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] 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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] 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.
gauthierpetetin
added a commit
to MetaMask/metamask-extension
that referenced
this issue
Aug 30, 2024
…e anymore (#26777) ## **Description** The description of bug report issues created by this [Github action](https://github.com/MetaMask/metamask-extension/blob/develop/.github/workflows/create-bug-report.yml) wasn't up-to-date anymore. It was still referencing Zenhub which we don't use anymore. ## **Related issues** Fixes: Same PR for Mobile repo: MetaMask/metamask-mobile#10903 ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** See description of this [example issue](gauthierpetetin-test/repo_test#198). <img width="660" alt="Screenshot 2024-08-29 at 17 05 24" src="https://github.com/user-attachments/assets/2929ff32-b6b5-41d2-9ff0-ce65acc29620"> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] 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. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] 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. --------- Co-authored-by: seaona <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is this bug report issue for?
This issue is used to track release dates on this Github Project board, which content then gets pulled into our metrics system.
This issue is also used by our Zapier automations, to determine if automated notifications shall be sent on Slack for release
1.2.9. Notifications will only be sent as long as this issue is open.Who created and/or closed this issue?
This issue was automatically created by a GitHub action upon the creation of the release branch
release/1.2.9, indicating the release was cut.This issues gets automatically closed by another GitHub action, once the
release/1.2.9branch merges intomain, indicating the release is prepared for store submission.The text was updated successfully, but these errors were encountered: