Skip to content

ci: apply e2e readiness label for PRs#29650

Merged
jvbriones merged 1 commit into
mainfrom
ci-pr-no-e2e
May 4, 2026
Merged

ci: apply e2e readiness label for PRs#29650
jvbriones merged 1 commit into
mainfrom
ci-pr-no-e2e

Conversation

@jvbriones

@jvbriones jvbriones commented May 4, 2026

Copy link
Copy Markdown
Contributor

Description

Automatically applies the pr-not-ready-for-e2e label to newly opened PRs, but only if the PR is opened between 13:00 and 17:00 UTC (15:00–19:00 CEST).

Changelog

CHANGELOG entry:

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

Performance checks (if applicable)

  • I've tested on Android
    • Ideally on a mid-range device; emulator is acceptable
  • I've tested with a power user scenario
    • Use these power-user SRPs to import wallets with many accounts and tokens
  • I've instrumented key operations with Sentry traces for production performance metrics

For performance guidelines and tooling, see the Performance Guide.

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
Low risk GitHub Actions trigger change; it only broadens when the labeling workflow runs (now excluding release/**).

Overview
The auto-label workflow is no longer limited to temporary test-e2e-readiness-label-** branches and will now run for newly opened PRs on all branches except release/**, where it is explicitly ignored.

Reviewed by Cursor Bugbot for commit 20c6ddf. Bugbot is set up for automated code reviews on this repo. Configure here.

@jvbriones jvbriones requested a review from a team as a code owner May 4, 2026 12:04
@jvbriones jvbriones added the no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed label May 4, 2026
@github-actions

github-actions Bot commented May 4, 2026

Copy link
Copy Markdown
Contributor

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.

@metamaskbotv2 metamaskbotv2 Bot added the team-qa QA team label May 4, 2026
@sonarqubecloud

sonarqubecloud Bot commented May 4, 2026

Copy link
Copy Markdown

@jvbriones jvbriones enabled auto-merge May 4, 2026 13:05
@jvbriones jvbriones added this pull request to the merge queue May 4, 2026
Merged via the queue into main with commit b3d1f40 May 4, 2026
107 of 109 checks passed
@jvbriones jvbriones deleted the ci-pr-no-e2e branch May 4, 2026 13:24
@github-actions github-actions Bot locked and limited conversation to collaborators May 4, 2026
@metamaskbotv2 metamaskbotv2 Bot added the release-7.77.0 Issue or pull request that will be included in release 7.77.0 label May 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed release-7.77.0 Issue or pull request that will be included in release 7.77.0 size-XS team-qa QA team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants