Why am I getting a Forge Laravel 505 server error after repo reset

Question

I was updating a website and I am now getting a 505 server error when I try to reload the page. (I am on a Statamic CMS and using Forge Laravel!)

I haven't changed much but I did, unfortunately, mess up the repo so had to reset it too an old commit. The issue happened before the reset and I thought going back to an old commit would work things out.

This is what the .htaccess file looks like,

<IfModule mod_rewrite.c>
<IfModule mod_negotiation.c>
    Options -MultiViews -Indexes
</IfModule>

RewriteEngine On

# Handle Authorization Header
RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Redirect Trailing Slashes If Not A Folder...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} (.+)/$
RewriteRule ^ %1 [L,R=301]

# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]
</IfModule>

Then the app_debug logs aren't useful leading me to think something has happened with the server maybe?

--Update--

Just spotted on Forge it is saying I am, "Your branch is ahead of 'origin/master' by 16 commits."

Image off it below Screen shot off development log

Guessing the repo is still messed up?

I found this and will follow the advice there, Your branch is ahead of 'origin/master' by 3 commits

--Second Update--

I got the repo back on track, or I hope I did, but still getting the 505 server error so back to the drawing board to whats the issue!

Could it just be I have taxed the server but commiting too much?

Thanks for your help, Zack