chore: INFRA-2925:Adding github action to merge stable to main on comment

[XxdpavelxX]

Description

Allows you to merge stable-main-X.Y.Z -> base main PRs on comment "Merge my PR"

Successful Negative tests:
Not Merging on Incorrect comment: consensys-test#55, https://github.com/consensys-test/metamask-mobile-test-workflow/actions/runs/19683528967
Not Merging from wrong source branch: consensys-test#53, https://github.com/consensys-test/metamask-mobile-test-workflow/actions/runs/19575100357/job/56058172525
Not Merging into wrong target branch: consensys-test#54, https://github.com/consensys-test/metamask-mobile-test-workflow/actions/runs/19575460777/job/56059417843
Not Merging on unapproved PR: consensys-test#55, https://github.com/consensys-test/metamask-mobile-test-workflow/actions/runs/19709760888
Not Merging on approver not in Release Team: consensys-test#55, https://github.com/consensys-test/metamask-mobile-test-workflow/actions/runs/19709971385

Desired Successful test: consensys-test#55, https://github.com/consensys-test/metamask-mobile-test-workflow/actions/runs/19710071272/job/56467981022

Changelog

CHANGELOG entry: None

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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 format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). 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.

---

Note

Add GitHub Actions workflow to auto-merge PRs on exact "Merge my PR" comment from MEMBER/OWNER using reusable workflow.

• CI/GitHub Actions:
  • New workflow /.github/workflows/merge-approved-pr.yml:
    • Triggers on issue_comment (created) for PRs.
    • Merges when comment is exactly Merge my PR and commenter is MEMBER or OWNER.
    • Reuses MetaMask/github-tools/.github/workflows/merge-approved-pr.yml@30baa9d....
    • Passes pr-number from event and uses METAMASK_MOBILE_BRANCH_SYNC_TOKEN as github-token.

^{Written by Cursor Bugbot for commit e56215b. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sethkfman]

Do we want collaborators to be able to merge?

[XxdpavelxX]

I assumed so if the PR is approved by a release team member, but if not then let me remove that.

[sethkfman]

I see the collaborator is anyone who can write to the repo. Should we constrain this to a specific team like Release Team?

[XxdpavelxX]

I've removed collaborator.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

This PR adds a new GitHub Actions workflow file (.github/workflows/merge-approved-pr.yml) that provides a convenience feature for merging approved PRs via a comment command.

Key observations:

1. This is a completely new file (not modifying existing code)
2. The workflow is purely for GitHub automation - it triggers when a comment "Merge my PR" is posted by a MEMBER or OWNER on a PR
3. It calls a reusable workflow from MetaMask/github-tools repository to handle the actual merge
4. This workflow does NOT affect:
   • Application code
   • Build processes
   • Test infrastructure
   • E2E testing frameworks
   • Any runtime behavior of the MetaMask Mobile app
5. No other files in the codebase reference this workflow
6. This is a developer workflow tool that only impacts the GitHub PR merge process

Impact Assessment:

• Zero impact on application functionality
• Zero impact on E2E test execution or infrastructure
• This is pure CI/CD automation for repository management
• The workflow only affects how PRs are merged, not what code is merged or how it's tested

Risk Level: Low - This is a documentation/infrastructure-only change with no impact on the application or its testing.

Recommendation: No E2E tests are necessary for this change. The workflow itself can be validated through GitHub Actions execution, but it doesn't require functional testing of the MetaMask Mobile application.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Gudahtt]

LGTM!

[sethkfman]

LGTM