actions/Github-Actions-Runner
Watch
1
0
Fork
You've already forked Github-Actions-Runner
 0
Code Pull requests Packages 1 Activity Actions

Drop the dead .trunk/configs submodule stanza #10

Merged
geusebio merged 1 commit from chore/drop-dead-trunk-submodule-stanza into main 2026-09-01 10:25:54 +00:00
Conversation 0 Commits 1 Files changed 1 -3
geusebio commented 2026-09-01 10:18:32 +00:00
Owner
Copy link

The repo this submodule stanza points at is gone.

Grey.ooo/Opinionated-Trunk-Configuration no longer exists on git.grey.ooo (404, confirmed against a full enumeration of all 443 repos on the instance as an admin), and neither does its GitHub mirror matthewbaggett/Opinionated-Trunk-Configuration (404).

Nothing breaks today and nothing breaks from this change. The stanza is already inert: there is no gitlink for .trunk/configs in the index and no .trunk/ directory anywhere in the tree. git submodule iterates index gitlinks rather than .gitmodules, so clone --recurse-submodules, submodule sync --recursive and submodule update --init --recursive all succeed without ever contacting the dead URL - verified empirically against this exact stanza. This repo's workflows do not check out with submodules: true in any case.

The stanza was the only content of .gitmodules, so the file is removed rather than edited.

Trunk was removed from this repo previously and is not being replaced - the estate's remaining trunk users inline .trunk/configs/ as plain committed files. The only other leftover here is the stale checks: write # For trunk to post annotations comment in build.yml, left in place as it is only a comment.

This repo push-mirrors to github.com/grey-ooo/Github-Actions-Runner, so merging here clears the identical stanza on that copy too.

The repo this submodule stanza points at is gone. `Grey.ooo/Opinionated-Trunk-Configuration` no longer exists on git.grey.ooo (404, confirmed against a full enumeration of all 443 repos on the instance as an admin), and neither does its GitHub mirror `matthewbaggett/Opinionated-Trunk-Configuration` (404). **Nothing breaks today and nothing breaks from this change.** The stanza is already inert: there is no gitlink for `.trunk/configs` in the index and no `.trunk/` directory anywhere in the tree. `git submodule` iterates index gitlinks rather than `.gitmodules`, so `clone --recurse-submodules`, `submodule sync --recursive` and `submodule update --init --recursive` all succeed without ever contacting the dead URL - verified empirically against this exact stanza. This repo's workflows do not check out with `submodules: true` in any case. The stanza was the only content of `.gitmodules`, so the file is removed rather than edited. Trunk was removed from this repo previously and is not being replaced - the estate's remaining trunk users inline `.trunk/configs/` as plain committed files. The only other leftover here is the stale `checks: write # For trunk to post annotations` comment in `build.yml`, left in place as it is only a comment. This repo push-mirrors to `github.com/grey-ooo/Github-Actions-Runner`, so merging here clears the identical stanza on that copy too.
Drop the dead .trunk/configs submodule stanza
All checks were successful
Build / Build Builder (push) Successful in 20m38s
Details
6687a93a8a 
The stanza points at Grey.ooo/Opinionated-Trunk-Configuration, which no
longer exists on git.grey.ooo (nor as the GitHub mirror). It has been
inert for some time regardless: there is no gitlink for .trunk/configs
in the index and no .trunk/ directory in the tree, so git never reads
the URL - `git submodule` iterates index gitlinks, not .gitmodules.

This stanza was the only content of the file, so the file goes with it.
Trunk itself was removed from this repo previously; the only other
trace is the stale `checks: write # For trunk to post annotations`
comment in build.yml.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
actions/Github-Actions-Runner!10
No description provided.