Issue preventing deploy via GitHub Actions about blog HOT 3 CLOSED

I think that the submodule might also be causing problems. I used to deploy directly from the public folder of my dev environment before I was able to run github actions.

from blog.

It seems like I still have some issues. I need to set up the deploy key correctly, and I'm not sure that I have it done yet.

=================== Publish to GitHub Pages ===================
Pushing Builds to [email protected]:sermonarchives/sermonarchives.github.io.git:master
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m
Initialized empty Git repository in /github/workspace/dist/.git/
error: pathspec 'master' did not match any file(s) known to git
Switched to a new branch 'master'
Files to Commit:12
Load key "/root/.ssh/id_rsa": invalid format
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

from blog.

The issue was, among other things, bad deploy keys.
PRs #40 through #49 detail the process of me flailing around until things were fixed. I did a little cleanup along the way, mostly of submodules that didn't need to exist any more.

This issue has now been resolved.

from blog.