got this on a new repo i just made (on knot1.tangled.sh + doesnt affect other older repos) repo is tangled.sh/@vielle.dev/... (the alert is about spindle.tangled.sh, idk if yall havent updated it yet or if my accounts cursed or smthn lmao) cc @tangled.sh
ok wait no the spindle thing was cause i had it in my list of spindles as one i administer ??? idk why i did that the error message should prolyl be better tho
you must have tried to register that spindle.tangled.sh as a spindle by yourself. you can just delete it and the warning will go away.
okay other repos SEEM fine but all folders get a 503 knot unavaliable?? and i can manually go to all the files in the first repo ???
for the other repo, did you by any chance push to a branch that was not main? we have a PR open to fix this!
my main branch is master, but thats the only branch in the 503 repo (tangled.sh/@vielle.dev/...) (turns out its only that and /dong which are broken i think)
this has been fixed now!
🔥🔥🔥
aha, there is an open PR with a fix! I'll get this sorted tomorrow. for now you can edit the default branch in repo settings and all should be fine.
o7 ty that seems to be the issue with the first repo want me to make an issue for the submodules regression too?
(submodules have never worked, we are yet to support it)
i seem to remember it at least not throwing a 503? i think it just showed an empty folder or something although i might be misremembering probably worth at least adding an error explaining its a submodule or smthn if its not nightmarish to do
so /dong: cant see the homepage bc "knot needs updated" but i can manually browse files and folders if i change the url /server-config i can see the homepage but any folders return a 503
wait no /server-config seems to just be a git submodules issue actually its any folder except /caddy thats broken in that one since theyre all submodules
yeah we don't have support for submodules yet.