ci: make local e2e the merge gate

[piotr-iohk]

Related to synonymdev/bitkit-e2e-tests#221 (PR B)

This PR:

1. Drops staging jobs from the local merge-gate workflow so required e2e-status is local-only
2. Keeps e2e-staging.yml on schedule and dispatch (no PR trigger)
3. Runs migration on release-* PRs and posts the same Slack summary as staging

Description

Staging stays off the merge gate. Feature PRs no longer wait on stag0. Local grep is @transfer_2 instead of blob @transfer. Staging shards stay @multi_address_2, @pubky, @transfer_max (@transfer_1 later). Slack checkout uses the resolved e2e-tests branch so a same-named branch can test slack_summary.py.

Migration: pull_request runs only when head or base starts with release-. Slack posts on schedule and on dispatch when post_to_slack is true, using SLACK_WEBHOOK_URL_STAGING.

Linked Issues/Tasks

synonymdev/bitkit-e2e-tests#221

Design

N/A — no UI changes.

Screenshot / Video

N/A

QA Notes

Manual Tests

N/A

Automated Checks

• Workflow YAML only. After merge: a feature PR should go green on e2e-status without staging jobs.
• After merge: gh workflow run e2e-staging.yml still works; migration on a release-* PR should run; nightly/dispatch with post_to_slack posts to #bitkit-staging-nightly.

[greptile-apps]

Confidence Score: 5/5

The PR has no newly identified blocking defects, although the existing non-blocking concern about running a mutable external script with the Slack webhook remains unresolved.

Findings

1.   Mutable Script Receives Secret ▶

Summary

The PR makes local E2E tests the pull-request merge gate, removes staging jobs from that gate, and adds release-branch migration runs with optional Slack reporting.

• Removes staging build and test jobs from .github/workflows/e2e-tests.yml.
• Restricts the required e2e-status result to local E2E shards.
• Runs migration jobs for non-draft pull requests whose head or base starts with release-.
• Adds scheduled and opt-in dispatched migration summaries to Slack.
• Uses the resolved E2E-tests branch when obtaining Slack summary scripts.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    PR[Pull request] --> Detect[Detect code changes]
    Detect --> Local[Build and run local E2E]
    Local --> Gate[Required e2e-status gate]

    Release[release-* pull request] --> Migration[Migration E2E workflow]
    Schedule[Nightly schedule] --> Migration
    Dispatch[Manual dispatch] --> Migration
    Migration --> Report{Schedule or post_to_slack?}
    Report -->|Yes| Slack[Post migration summary]

Loading

_{Reviews (2) · Last reviewed commit: "ci: checkout slack script from resolved ..."}

[ovi-reviewer]

Verdict: ✅ Approve

---

Review: diff 2 files.
Counterpart synonymdev/bitkit-android#1268: equivalent.

Findings:
N/A

Audit:
Skipped - no security surface in the diff (score 0, threshold 3).

---

Reviewed by gpt-5.6-sol-high via gh-pr-review-loop skill
Commands: @ovi-reviewer test · retest · audit (author or owner)

[ovitrif]

approved
merging, integration tests ci failure is known env issue, not broken by this PR