expo-github-action
Expo GitHub Action makes it easy to automate EAS builds or updates
Runssource: GitHubTypeScriptMITcommit eab7a230208c
TypeScript, MIT licensed. The project labels itself: actions, cli, continuous delivery, continuous integration, expo and github actions.
expo-github-action runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install succeeds, all 115 Jest tests pass across 12 suites with 8 matching inline snapshots, and all 9 ncc-compiled action bundles (setup, preview, preview-comment, command, fingerprint, fingerprint-post, continuous-deploy-fingerprint, continuous-deploy-fingerprint-info, preview-build) are present and loadable.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- build script ncc.js failed because bun is not installed and prebuild step deleted node_modules2 minutes
- tests failed with TS2304: Cannot find name 'jest' / TS2593: Cannot find name 'describe' in all 12 test suites1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npx jest exited 0, 115 passed, 8 snapshots matched across 12 suites; node -e 'require("build/setup/index.js")' loaded the setup bundle and executed its action handler without errors
- Model tokens used
- 47,093
- Exact commit tested
- eab7a230208c
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Snapshots: 8 passed, 8 total Time: 8.134 s, estimated 9 s All 12 test suites pass with 115 tests and 8 snapshots. The build artifacts are compiled. Here's th… **Errors encountered and fixed:** 1. **tsconfig missing Jest types** — `tsconfig.json` extended `@tsconfig/node24` which only set `"t… 2. **ncc build script requires `bun`** — `/work/repo/ncc.js` runs `bun install --frozen-lockfile` i… tokens used 47,093 All 12 test suites pass with 115 tests and 8 snapshots. The build artifacts are compiled. Here's th… **Errors encountered and fixed:** 1. **tsconfig missing Jest types** — `tsconfig.json` extended `@tsconfig/node24` which only set `"t… 2. **ncc build script requires `bun`** — `/work/repo/ncc.js` runs `bun install --frozen-lockfile` i…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1 minute, faster than the median of the 10 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 11 actions projects Argusic has installed and timed, expo-github-action was the 4th fastest to reach a running state, and 6 of 11 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.02 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.05 |
Topics (from GitHub)
actionsclicontinuous-deliverycontinuous-integrationexpogithub-actions
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/expo-github-action)Questions
- Does expo-github-action run?
- Yes. expo-github-action runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test expo-github-action?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eab7a230208c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test expo-github-action?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does expo-github-action take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does expo-github-action need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing expo-github-action?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does expo-github-action compare with the alternatives?
- Of the 11 actions projects Argusic has installed and timed, expo-github-action was the 4th fastest to reach a running state, and 6 of 11 reached one at all.
- Where is the evidence for expo-github-action?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.