changed-files
:octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
Runssource: GitHubTypeScriptMITcommit 9c9e94395b39
TypeScript, MIT licensed. The project labels itself: actions, change detection, change detetion, changed file, changed files, ci, ci cd and conditional execution.
changed-files runs. An Argusic agent installed it in 10 minutes 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 with --legacy-peer-deps, TypeScript compilation completes with no errors, and all 65 tests pass across 4 test suites
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 100 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.
- getPreviousGitTag tests failed because repository has no git tags with expected SHAs4 minutes
- npm install peer dependency conflict (eslint-plugin-jest vs @typescript-eslint/eslint-plugin)2 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test exited 0, 65 passed across 4 test suites, tsc --noEmit and tsc both succeed
- Model tokens used
- 67,410
- Exact commit tested
- 9c9e94395b39
- 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.
exec /bin/sh -lc '# Final confirmation: run tests one more time and capture key output npm test 2>&1 | grep -E "Test Suites|Tests:|Snapshots:|Time:" | head -5' in /work/repo succeeded in 13153ms: Test Suites: 4 passed, 4 total Tests: 65 passed, 65 total Snapshots: 6 passed, 6 total Time: 11.811 s, estimated 15 s All 65 tests pass, TypeScript compiles cleanly, and the build succeeds. Here's the report: tokens used 67,410 All 65 tests pass, TypeScript compiles cleanly, and the build succeeds. Here's the report:
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 10 minutes.
- 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 10 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
Topics (from GitHub)
actionschange-detectionchange-detetionchanged-filechanged-filescici-cdconditional-executioncontinuous-deliverycontinuous-integrationgithubgithub-actionsmodifiedmodified-filesmonoreporestore-filessubmodulesworkflowsyaml-files
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/changed-files)Questions
- Does changed-files run?
- Yes. changed-files runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test changed-files?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9c9e94395b39. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test changed-files?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does changed-files take to install?
- 10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does changed-files need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing changed-files?
- 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.
- Where is the evidence for changed-files?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.