Bug Report

Description

Hi I think I encountered the same problem like described in the bug #1074 today.
I tried to run semantic release on an action with my self hosted gitea instance that is hosted via http.

Here is my remote config

[semantic_release.remote]
name = "origin"
domain = "http://gitea:3000"
type = "gitea"
insecure = true

what I noticed during my investigations was that gitea sets the same env variables like github. So the following environment variables are set in the pipeline:

• GITHUB_SERVER_URL
• GITHUB_API_URL

For testing I tried to unset the two env vars before executing semantic release it worked.

unset GITHUB_SERVER_URL
unset GITHUB_API_URL

I assumtion is that semantic release somehow does a remote auto config based on the env variables.
But I do not understand the code enough to validate that theory.

It can also be reproduced without a cicd pipeline
Just set the GITHUB_SERVER_URL env variable with a http schema and run semantic-release --version

$env:GITHUB_SERVER_URL = "http://gitea:3000"
semantic-release --version

This already leads to the same issue on my local windows pc

Hope this info helps someone with fixing the issue.

BR
Philipp