Hmm there are a lot of pieces to your question.
The thing that stands out is custom domain.
If your idea is to serve on the root of
Then you do want an empty baseurl.
It doesn’t matter whether your repo ends up being on a subpage or the root on GH Pages, because the end result will be on the root. Therefore you should set
url: https://agileinaction.com
baseurl: ''
Even if it ends up being on
MyOtherAccount.github.io/agileinactionsite
As the custom domain lack of subpath.
If it weren’t for that need, I’d say set baseurl in the config. And have that set on Forestry config if needed and for local use so you use subpath throughout.
I don’t know why you need to build to a separate repo. I find building to gh-pages branch works
An advantage is that maybe you have the one repo and it’s GH Pages set up as your staging site. And you tell Google not to crawl it. Then push a bunch of commits or PRs there. And use that as your preview. Without Forestry to handle a preview.
Then use GH Actions to build the site across repos selectively like on a tag made, commit to master, or “ci” in commit message