[E2E] Remove /e2e comment trigger from CI workflows (#720)

Author: CassioMG

.github/workflows/android-e2e.yml

@@ -6,8 +6,6 @@ on:
     types: [opened, synchronize, reopened, ready_for_review]
   push:
     branches: [main, release, "v*.*.*"]
-  issue_comment:
-    types: [created]
   workflow_dispatch:
     inputs:
       ref:
@@ -77,19 +75,11 @@ jobs:
     name: Build Android APK
     runs-on: ubuntu-latest-16-cores
     timeout-minutes: 120
-    # Run on PR "/e2e" comments, or on normal triggers (PR, push, workflow_dispatch)
-    if: |
-      (github.event_name == 'issue_comment' && github.event.issue.pull_request && github.event.comment.body == '/e2e') ||
-      github.event_name != 'issue_comment'
-
     steps:
       - name: Checkout repo
         uses: actions/checkout@v5
         with:
-          ref:
-            ${{ github.event.inputs.ref || (github.event_name == 'issue_comment'
-            && format('refs/pull/{0}/head', github.event.issue.number)) ||
-            github.ref }}
+          ref: ${{ github.event.inputs.ref || github.ref }}
 
       - name: Make scripts executable
         run: find scripts -type f -exec chmod +x {} \;
@@ -240,10 +230,7 @@ jobs:
       - name: Checkout repo
         uses: actions/checkout@v5
         with:
-          ref:
-            ${{ github.event.inputs.ref || (github.event_name == 'issue_comment'
-            && format('refs/pull/{0}/head', github.event.issue.number)) ||
-            github.ref }}
+          ref: ${{ github.event.inputs.ref || github.ref }}
 
       - name: Make scripts executable
         run: find scripts -type f -exec chmod +x {} \;

.github/workflows/ios-e2e.yml

@@ -6,8 +6,6 @@ on:
     types: [opened, synchronize, reopened, ready_for_review]
   push:
     branches: [main, release, "v*.*.*"]
-  issue_comment:
-    types: [created]
   workflow_dispatch:
     inputs:
       ref:
@@ -69,19 +67,11 @@ jobs:
     name: Build iOS App
     runs-on: macos-26-xlarge
     timeout-minutes: 120
-    # Run on PR "/e2e" comments, or on normal triggers (PR, push, workflow_dispatch)
-    if: |
-      (github.event_name == 'issue_comment' && github.event.issue.pull_request && github.event.comment.body == '/e2e') ||
-      github.event_name != 'issue_comment'
-
     steps:
       - name: Checkout repo
         uses: actions/checkout@v5
         with:
-          ref:
-            ${{ github.event.inputs.ref || (github.event_name == 'issue_comment'
-            && format('refs/pull/{0}/head', github.event.issue.number)) ||
-            github.ref }}
+          ref: ${{ github.event.inputs.ref || github.ref }}
 
       - name: Make scripts executable
         run: find scripts -type f -exec chmod +x {} \;
@@ -237,10 +227,7 @@ jobs:
       - name: Checkout repo
         uses: actions/checkout@v5
         with:
-          ref:
-            ${{ github.event.inputs.ref || (github.event_name == 'issue_comment'
-            && format('refs/pull/{0}/head', github.event.issue.number)) ||
-            github.ref }}
+          ref: ${{ github.event.inputs.ref || github.ref }}
 
       - name: Make scripts executable
         run: find scripts -type f -exec chmod +x {} \;

e2e/README.md

@@ -46,13 +46,13 @@ E2E tests run **locally** (with Maestro CLI + simulator/emulator) or in **CI**
 
 Detailed guides live in `e2e/docs/`:
 
-| Topic                     | File                                                          | Description                                                                                    |
-| ------------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| **CI & Triggers**         | [ci-and-triggers.md](docs/ci-and-triggers.md)                 | When tests run, branch filters, manual runs (workflow_dispatch, `/e2e`), CI matrix parallelism |
-| **Local Setup & Env**     | [local-setup-and-env.md](docs/local-setup-and-env.md)         | `.env` for E2E, `E2E_TEST_RECOVERY_PHRASE`, how secrets/vars are used in CI                    |
-| **Running Tests**         | [running-tests.md](docs/running-tests.md)                     | Run in CI vs locally, single flow by platform + name                                           |
-| **Artifacts & Debugging** | [artifacts-and-debugging.md](docs/artifacts-and-debugging.md) | Artifact layout, logs, recordings, screenshots, how to debug failures                          |
-| **Creating Tests**        | [creating-tests.md](docs/creating-tests.md)                   | Maestro YAML (API), Maestro Studio, recording flows, best practices (e.g. prefer `testID`)     |
+| Topic                     | File                                                          | Description                                                                                |
+| ------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
+| **CI & Triggers**         | [ci-and-triggers.md](docs/ci-and-triggers.md)                 | When tests run, branch filters, manual runs (workflow_dispatch), CI matrix parallelism     |
+| **Local Setup & Env**     | [local-setup-and-env.md](docs/local-setup-and-env.md)         | `.env` for E2E, `E2E_TEST_RECOVERY_PHRASE`, how secrets/vars are used in CI                |
+| **Running Tests**         | [running-tests.md](docs/running-tests.md)                     | Run in CI vs locally, single flow by platform + name                                       |
+| **Artifacts & Debugging** | [artifacts-and-debugging.md](docs/artifacts-and-debugging.md) | Artifact layout, logs, recordings, screenshots, how to debug failures                      |
+| **Creating Tests**        | [creating-tests.md](docs/creating-tests.md)                   | Maestro YAML (API), Maestro Studio, recording flows, best practices (e.g. prefer `testID`) |
 
 ---
 

e2e/docs/ci-and-triggers.md

@@ -9,7 +9,6 @@ covers when they run, how to trigger them manually, and how the CI matrix works.
 flowchart TD
   PR[Pull request] --> BR{Target branch?}
   PU[Push] --> BR
-  IC[Comment /e2e on PR] --> RUN
   WD[workflow_dispatch] --> RUN
   BR --> |main, release, v*.*.*| RUN[Run E2E workflow]
   BR --> |Other| SKIP[Skip]
@@ -19,26 +18,20 @@ flowchart TD
 | --------------------- | -------------------------------------------------------------------------------------------------- |
 | **Pull request**      | `opened`, `synchronize`, `reopened`, `ready_for_review` on `main`, `release`, or `v*.*.*` branches |
 | **Push**              | Same branches as above                                                                             |
-| **Issue comment**     | Comment **exactly** `/e2e` on a PR (runs on that PR's head)                                        |
 | **workflow_dispatch** | Manual run from **Actions** tab                                                                    |
 
 **Branch patterns**: `v*.*.*` matches semantic versions (e.g. `v1.2.3`), not
 arbitrary names like `vrandombranch`.
 
 ## Manual runs
 
-### 1. workflow_dispatch
+Use **workflow_dispatch** to run E2E tests on demand:
 
 1. Open **Actions** → **Android E2E Tests** or **iOS E2E Tests**.
 2. Click **Run workflow**.
 3. Optionally set **ref** (commit hash) or leave empty for default branch.
 4. Run.
 
-### 2. Comment `/e2e` on a PR
-
-Comment **exactly** `/e2e` on a pull request. The workflow runs for that PR's
-head. Build and test jobs use the same ref.
-
 ## CI matrix & parallelism
 
 ```mermaid