create-pull-request

A GitHub action to create a pull request for changes to your repository in the actions workspace

Runssource: GitHubTypeScriptMITcommit 11e8dc7c9cc9

TypeScript, MIT licensed. The project labels itself: actions workspace, automation, ci cd, create pull request, github action, pull request and workflow.

create-pull-request runs. An Argusic agent installed it in 2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 68 tests pass (18 unit + 50 integration): Node 24 via nvm, git daemon populated with test repos on port 9418, test paths relocated to /tmp/git-test/, build produces dist/index.js via ncc

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.37 (measured)
recorded runs
2
last tested
stars
2,874
forks
554
open issues
19
watchers
24
size
36 MB
created
last push

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.

Time lost to each failure while testing create-pull-request, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • git daemon process killed between exec calls / port 9418 in TIME_WAIT3 minutes
  • Node v18 does not satisfy >=24.4.0 engine requirement2 minutes
  • Integration test hardcodes /git/ paths not present in container1 minute
Install time
2 minutes
Cold machine to finish
36 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm run test:unit passed (18/18, 2 suites); npx jest int --runInBand passed (50/50, 3 suites)
Model tokens used
910,284
Exact commit tested
11e8dc7c9cc9
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Unit tests: 18/18 passed
Integration tests: 50/50 passed
Total: 68/68 tests passed
Changes: 4 test files patched (git/ -> tmp/git-test/ paths)
exec
/bin/sh -lc "echo -n 'ARGUSIC_RESULT:'
echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2, \"errors\":…
 succeeded in 0ms:
All done. The repository is fully operational with all 68 tests passing (18 unit + 50 integration).…
tokens used
910,284
All done. The repository is fully operational with all 68 tests passing (18 unit + 50 integration).…

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 2 minutes.
  • Recovered from all 3 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.

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 2 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.37
Argusic Runner1/3Runs100.000.16

Topics (from GitHub)

actions-workspaceautomationci-cdcreate-pull-requestgithub-actionpull-requestworkflow

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/create-pull-request.svg)](https://argusic.com/subject/create-pull-request)

Questions

Does create-pull-request run?
Yes. create-pull-request runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test create-pull-request?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 11e8dc7c9cc9. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test create-pull-request?
The run that produced this verdict cost $0.37: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does create-pull-request take to install?
2 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 create-pull-request need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing create-pull-request?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for create-pull-request?
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.

Discussion