Let owners give runs more git history
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by tracing how runs receive the one-commit repository snapshot and where repository and per-job settings are defined. The issue does not name files or tests, so locate those entry points first; then map how history metadata and old file contents would reach the sandbox. Done means owners can configure the proposed history levels safely, with the default still exposing one commit and the settings page clearly describing Full access.
Written by the indexing model from the issue text.
Description
Runs now get a git repository in /workspace with one commit of the files and no parents. That covers git status, git diff and git rev-parse. Some skills want history:
- skills that date work by commit, such as finding abandoned projects
- skills that measure the age of debt with
git logandgit blame - changelog and release-note skills that read commits since the last tag
Proposal
An owner setting per repository, with an optional per-job override. Repository config can only ask for it.
| Setting | status, diff |
log with dates and authors |
blame, old file contents |
Deleted secrets |
|---|---|---|---|---|
| One commit (default) | yes | no | no | not exposed |
| Metadata only | yes | yes | no | only those in commit messages |
| Full | yes | yes | yes | exposed |
Metadata only is a partial clone (--filter=blob:none) with no promisor remote in the sandbox. Commands that need an old file's contents fail, which is the point.
Why one commit stays the default
- Deleted secrets. A key that was committed and later removed is still in history. With history in the sandbox the agent can read it, the model provider sees it, and a prompt injection in repository content can put it in a report, issue or pull request description. The sandbox having no network does not help, because the agent's own output is the way out.
- Size. Snapshots are capped at 64 MiB. History for older repositories can be gigabytes, uploaded for every run.
- Exposure. Author emails, deleted files and old branches that the owner never chose to share with a scheduled job.
Open questions
- How deep: whole history, or the last N commits or days?
- Should the real commit SHA be kept, so
git rev-parse HEADmatches GitHub? That needs the real commit object, and its parents' objects for anything past one commit. - Where history comes from: the repository mirror on the control plane, packed per run, or a cached pack per commit.
- The settings page should say plainly what Full exposes.
Found in a study of 50 public skills. 4 of 15 skills whose git commands failed used history. The others needed only a single commit.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 322
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 piotrekno1/second-shift
-
code-review secondshift
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
piotrekno1/second-shift#419 ·
Maintainers usually reply within 1 day
-
area: deployment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piotrekno1/second-shift#310 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 46/100
piotrekno1/second-shift#421 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#420 ·
Maintainers usually reply within 1 day
-
Fix failed-delivery retries on PostgreSQLPossibly taken @piotrekno1 claimed this today. Opencode-review fix-approved secondshift
Difficulty 3/5 1-2 days Newbie friendliness 35/100
piotrekno1/second-shift#418 ·
Maintainers usually reply within 1 day
All issues in piotrekno1/second-shift
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day