fix(ci): re-run PR size check on base retarget

[NicolasMassart]

Description

check-pr-max-lines could report a stale/incorrect size label (e.g. size-XL) after a stacked PR was rebased onto main and its base branch retargeted. The workflow only re-ran on opened | reopened | synchronize, so a base change alone never triggered a fresh check against the new base.

This adds edited to the pull_request trigger types, gated so the job only re-runs for base-branch edits (github.event.changes.base != null), not unrelated title/body edits.

Related fix in the shared pr-line-check action (resolves the live PR base instead of trusting the webhook payload): MetaMask/github-tools#273

Changelog

CHANGELOG entry: null

Related issues

Refs: MCWP-747

Manual testing steps

Feature: PR size check re-runs on base retarget

  Scenario: a stacked PR is rebased onto main and its base is retargeted
    Given a PR is stacked on another branch and the size check has already passed
    When the PR head is rebased onto main and the PR base is retargeted to main
    Then the check-pr-max-lines check re-runs and reports the correct size label against main

Screenshots/Recordings

N/A - CI workflow change, no UI impact.

Before

N/A

After

N/A

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.

Performance checks (if applicable)

N/A - CI workflow-only change, no app runtime impact.

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

Low Risk
CI trigger-only change with no app, auth, or data impact; edited may also run the job on title/body edits.

Overview
check-pr-max-lines now listens for pull_request edited in addition to opened, reopened, and synchronize.

That lets the shared pr-line-check action run again when a PR is updated without a new push—e.g. after retargeting the base branch following a rebase—so size labels reflect the diff against the current base instead of staying stale.

^{Reviewed by Cursor Bugbot for commit 756f1cf. Bugbot is set up for automated code reviews on this repo. 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.

[metamask-ci]

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

• Pre-merge author checklist has only 5 of the required 8 items. Every checklist row must be present and consciously checked — do not delete rows.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

[metamask-ci]

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

• PR body does not match pull-request-template.md (one or more section headings are missing). See https://github.com/MetaMask/metamask-mobile/blob/main/.github/scripts/shared/pr-template-checks.ts#L15-L23.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0891e2d. Configure here.}

[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!