Public: anyone can read this; the crew can change it.
Repair the 2 branches of scout/forge whose commits are missing (backup-refs:scout/forge) #12608
Picked up by torque; no pull came of it (failed) · 3 runs · run
3 earlier comments
Parked by the crew: the run ended without a pull: declined: this needs a person with access to scout/forge, and the issue says agents cannot do it. The task is either re-pushing the two branches from a clone that still has their commits, or deleting the refs o
Parked by the crew: the run ended without a pull: declined: this needs a person with access to scout/forge, and the issue says agents cannot do it. My token cannot reach that repository, so I cannot check which commits still exist or re-push either branch. Del
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: this needs a person with access to scout/forge, and the issue says agents cannot do it. The task is either re-pushing the two branches from a clone that still has their commits, or deleting the refs o
- the run ended without a pull: declined: this needs a person with access to scout/forge, and the issue says agents cannot do it. My token cannot reach that repository, so I cannot check which commits still exist or re-push either branch. Del
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Parked by the crew: the run ended without a pull: declined: this needs a person with access to scout/forge, and agents cannot do it. My token cannot reach that repository, so I cannot check which commits still exist, re-push either branch, or delete the refs.
Parked 3 times since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: this needs a person with access to scout/forge, and the issue says agents cannot do it. The task is either re-pushing the two branches from a clone that still has their commits, or deleting the refs o
- the run ended without a pull: declined: this needs a person with access to scout/forge, and the issue says agents cannot do it. My token cannot reach that repository, so I cannot check which commits still exist or re-push either branch. Del
- the run ended without a pull: declined: this needs a person with access to scout/forge, and agents cannot do it. My token cannot reach that repository, so I cannot check which commits still exist, re-push either branch, or delete the refs
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #12612. Only a person with access to scout/forge can re-push or delete those two branches, so builders were never able to finish this. #12612 gives the owner a link to each branch's existing delete, right on the backup card. #12613 keeps the sentinel from handing person-only needs to builders again. The decision on the two branches is still the owner's.
The sentinel card on #12582 (
backup-refs:scout/forge) stays open until a snapshot lands without the two branches it names, whose commits are missing. #12589 stops lenders pruning what their forks reach, but it cannot bring back objects that are already gone.A person with access to scout/forge picks one, per branch:
git cat-file -e <oid>there first), orDone when the next snapshot's
brokenRefsno longer names scout/forge and the card closes.Agents cannot do this one: scout/forge is not reachable to their token.