ci: start the app tests from run tags only on f/ branches (#7768)

.github/workflows/desktop-linux.yml

@@ -4,7 +4,8 @@ name: desktop-linux
 on:
   push:
     branches:
-      - "**"
+      # only f/ branches, so other branches' pull requests don't list skipped runs; elsewhere, run it by hand
+      - "f/*"
       # a squash merge's message lists the merged commits' subjects, with their tags
       - "!master"
       - "!stable"

.github/workflows/ios-sim.yml

@@ -3,7 +3,8 @@ name: ios-sim
 on:
   push:
     branches:
-      - '**'
+      # only f/ branches, so other branches' pull requests don't list skipped runs; elsewhere, run it by hand
+      - 'f/*'
       # a squash merge's message lists the merged commits' subjects, with their tags
       - '!master'
       - '!stable'

scripts/ci/README.md

@@ -4,7 +4,7 @@ Two workflows build the apps from a branch's own code and test them, only when a
 
 ## Run tags
 
-Put a tag in the message of the commit you push. Tags combine: each workflow runs everything its tags ask for.
+Put a tag in the message of the commit you push to a branch named `f/…`. Tags combine: each workflow runs everything its tags ask for.
 
 | Tag | iOS | Desktop |
 |---|---|---|
@@ -17,7 +17,7 @@ Put a tag in the message of the commit you push. Tags combine: each workflow run
 | `[ci-backend]`, with one of the above | also the test backend | also the test backend |
 | `[ci-release]`, with one of the above | — | also the latest release's onboarding, to tell a branch's failure from the runner's |
 
-Only the pushed head commit counts, and a tag counts anywhere in its message, body included: never write one in a message unless that push should run it. A push that asks for nothing starts no job and doesn't cancel a running test; a newer requested run on the same branch cancels the older one. Pushes to master and stable never start a run, because a squash merge's message lists the merged commits' subjects with their tags; run it by hand there.
+Only the pushed head commit counts, and a tag counts anywhere in its message, body included: never write one in a message unless that push should run it. A push that asks for nothing starts no job and doesn't cancel a running test; a newer requested run on the same branch cancels the older one. Tags start runs only on `f/…` branches, so pull requests from other branches don't list skipped runs; on any other branch, master and stable included, run a workflow by hand.
 
 ## Running a workflow by hand
 

scripts/ci/desktop-linux/README.md

@@ -4,7 +4,7 @@
 
 ## Running it
 
-The workflow runs only when asked, on any branch, by a run tag in the pushed commit's message or by hand from the Actions tab: [App tests on GitHub's runners](../README.md) lists the tags and inputs.
+The workflow runs only when asked: by a run tag in a commit pushed to an `f/…` branch, or by hand from the Actions tab on any branch. [App tests on GitHub's runners](../README.md) lists the tags and inputs.
 
 Every run builds the core library, and the backend when it's asked for, from the branch's own Haskell code. It reuses an earlier build only when the sources are unchanged, as an artifact of the same branch named after a hash of its sources (30 days): for the core `src/**`, `cabal.project`, `simplex-chat.cabal`, `PRIVACY.md` and the build scripts, for the backend `src/**`, the CLI's and the directory's sources, `cabal.project`, `simplex-chat.cabal` and its build script. So a branch that changes core and app code together tests both. The workflow saves no Actions caches, which this repository evicts within hours and shares with `build.yml`.
 

scripts/ci/ios-sim/README.md

@@ -4,7 +4,7 @@
 
 ## Running it
 
-The workflow runs only when asked, on any branch, by a run tag in the pushed commit's message or by hand from the Actions tab: [App tests on GitHub's runners](../README.md) lists the tags and inputs.
+The workflow runs only when asked: by a run tag in a commit pushed to an `f/…` branch, or by hand from the Actions tab on any branch. [App tests on GitHub's runners](../README.md) lists the tags and inputs.
 
 Results: the job logs, the Claude job's summary (Claude's usage) and the artifacts `ios-sim-smoke-test` (a screenshot, a 1000-px view and an accessibility tree per step, the app log), `ios-sim-backend-logs` and `ios-sim-claude-test` (the Claude job's smoke test in `smoke-test/`, and per session: `prompt.md`, `report.md`, `shots/`, `transcript.jsonl`, `usage.json`). Read them with `gh run view <id> --log` and `gh run download <id> -n <artifact>`.