fix(ci): remove stray digibyte submodule gitlink breaking actions/checkout - #175
Merged
ycagel merged 1 commit intoAug 5, 2026
Conversation
The digibyte/ folder was accidentally committed in cc92f5f as a submodule gitlink (mode 160000) without a matching .gitmodules entry, which caused actions/checkout to fail with: fatal: No url found for submodule path 'digibyte' in .gitmodules Remove the dangling gitlink from the index and ignore the local Core source checkout so CI/Pages workflows can check out submodules recursively without error.
ycagel
requested review from
DGBNOOB,
JaredTate,
bastiandriessen,
gto90 and
ycagel
August 5, 2026 01:24
bastiandriessen
approved these changes
Aug 5, 2026
bastiandriessen
left a comment
Collaborator
There was a problem hiding this comment.
Approve
This correctly fixes the broken submodule reference that is currently blocking all GitHub Pages deployments.
The analysis and the two-line change (git rm --cached digibyte + adding digibyte/ to .gitignore) are accurate and minimal.
Once this lands, the redesigned site will go live.
Ready to merge from me.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
actions/checkout@v4fails on this repo with:Example failing run: https://github.com/DigiByte-Core/DigiByte.org/actions/runs/30958026357
Root cause
The repo's tree contains a submodule gitlink at path
digibyte(mode160000, pinned to8a3fd47b943ff883e51bf988dc9bac92916274dc) but no matching.gitmodulesfile at the root. So wheneveractions/checkoutrunsgit submodule update --init --recursiveit can't resolve a URL for thedigibytepath and aborts.Verified with:
The gitlink was introduced accidentally (likely because a nested
.gitwas present inside a localdigibyte/working copy atgit addtime). The DigiByte Core source isn't part of the Jekyll website, so the gitlink is just dangling data.Fix
digibytegitlink from the tree (git rm --cached digibyte).digibyte/to.gitignoreso a local Core source checkout can't be re-added accidentally.Diff is only 2 files:
.gitignore(+3) and removal of thedigibytegitlink entry.Impact
submodules: trueorsubmodules: recursive.digibyte/working directories on contributors' machines are untouched (only the index entry is removed).Note on the "Node 20 deprecation" banner
The
Node 20 is being deprecatedline in the failing log is unrelated runner-level info and did not cause the failure.