TestFlight builds don't identify their source branch (any-branch dispatch already works)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
Research direction
Start with .github/workflows/build-ios-from-expo.yml and inspect the workflow_dispatch inputs and TestFlight upload step. Run the iOS Expo Build & Upload workflow for a branch, then verify the uploaded TestFlight build identifies its source branch and short SHA while main builds remain clean or explicitly identify main.
Written by the indexing model from the issue text.
Description
Rescoped 2026-09-14 — the original ask ("build any branch, not just main") already works: the iOS workflow (.github/workflows/build-ios-from-expo.yml) is plain workflow_dispatch, so the Run-workflow branch dropdown — or gh workflow run "iOS Expo Build & Upload" --ref <branch> — builds that branch's code. Nothing pins it to main, and the one-click main path is unchanged.
Remaining gap
Builds from different branches are indistinguishable in TestFlight. The workflow stamps only expo.ios.buildNumber = GITHUB_RUN_NUMBER; the branch name appears nowhere — not in the version, not in the test notes. Two builds from different feature branches (or a branch build vs. a main build) look identical to a tester.
Fix (small workflow change)
Stamp the source branch into the build so TestFlight builds are attributable:
- Put
<branch> @ <short-sha>into the TestFlight "What to Test" notes at upload time (preferred — no version-format constraints), or embed it in whatever build-metadata field the upload action supports - Keep main builds clean (plain notes or
main @ <sha>)
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 2
- Avg merge
- 17h 16m
- Merged PRs (30d)
- 20
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mieweb/pulse
-
area:ui bug
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
performance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:export area:player enhancement
-
upload: persist the claimed transport profile (TUS create → kill → direct-advertising server wedge) Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100