I took a look through the other threads before posting but found that they were resolved with either
ssh-add -K or specifying the correct branch. Both of which I am very well aware of.
As of today, upon deploying to production, I am getting the error that the repo on branch master cannot be accessed. This worked just last night. No changes have been made to my fork of trellis between then and now. I can, however, deploy the exact same repo to staging, which I believe to be confirming the correct setup of both the branch and the SSH Forwarding Agent.
Here are my verbose deployment logs for both the successful staging and unsuccessful production deployment attempts.
Does anyone have an idea as to what is happening here?
Thanks so much.