Git Gateway error

[fool]

This is actually a different problem you are running into than the ones in this thread. Check out this article for details on the change GitLab made that broke this last year, and offers a path to work around it:

How to mitigate changes to GitLab version 15.0 support for OAuth tokens

In GitLab version 15.0, support for OAuth tokens with no expiration date was removed (gitlab issue). This meant that using our Git Gateway service started to have a 2-hour time limit when configured with GitLab and OAuth. This was a breaking change for many of our users. You can mitigate this problem by using a Personal Access Token. The steps are: log into the GitLab UI and generate a token (User Settings > Access Tokens) create the token with the scopes you need. For NetlifyCMS users those …