jesseduffield / jesseduffield/lazygit

Unsupported git service (after renaming remote name)

Open
#3,997 5 comments 3 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
82.4k
Forks
3k
Avg merge
2d 18h
Merged PRs (30d)
19

Description

**Describe the bug**
My setup used to work, so when I pressed `o` to open an MR with GitLab, but since I renamed the remote from `origin` to a different name, I get this error now.

**To Reproduce**

1. Clone the repo
2. Add 2nd remote (my fork)
3. Rename `origin` to something else
4. Try to create MR with `o`

```yaml
services:
'gitlab.exmaple.com': gitlab:gitlab.example.com
```

**Expected behavior**
The MR url should open in my default browser

**Version info:**
```
❯ lazygit --version
commit=611fabde11d24d9acc71ee26077b9a1101f59f27, build date=2024-09-18T10:56:10Z, build source=binaryRelease, version=0.44.1, os=linux, arch=amd64, git version=2.47.0

❯ git --version
git version 2.47.0
```

**Additional context**
When I run lazygit with `-debug` in the logs output, I still see lazygit try to use the origin remote name

```
...
Oct 18 03:36:37 |DEBU| time to get behind base branch values for all branches: 49.980564ms
Oct 18 03:36:40 |DEBU| RunCommand command="git ls-remote --get-url origin"
Oct 18 03:36:40 |INFO| git ls-remote --get-url origin (2.410547ms)
```

```
❯ git remote -v
contra git@gitlab.example.com:contra/repo1.git (fetch)
contra git@.gitlabexample.com:contra/repo1.git (push)
rabin-io git@gitlab.example.com:rabin-io/repo1.git (fetch)
rabin-io git@gitlab.example.com:rabin-io/repo1.git (push)
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.