SSH configuration issue => pushing to the wrong repository. #29

New Issue

Closed

opened 2023-10-16 19:21:26 +02:00 by GNUtoo · 1 comment

GNUtoo commented

2023-10-16 19:21:26 +02:00

Member

Hi, when I push inside a repository I have:

$ git push forgejo HEAD:wip
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 2 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 1022 bytes | 1022.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote: 
remote: To create a merge request for wip, visit:
remote:   https://git.a-lec.org/GNUtoo/experimental-vms/-/merge_requests/new?merge_request%5Bsource_branch%5D=wip
remote: 
To forge.a-lec.org:GNUtoo/experimental-vms.git
   f6ee3b7..c8f6259  HEAD -> wip

It pushes to git.a-lec.org and my commit ends up on the gitlab forge.

But I used the forge.a-lec.org domain to push:

[gnutoo@primary_laptop experimental-vms]$ git remote get-url forgejo
git@forge.a-lec.org:GNUtoo/experimental-vms.git

Here's the relevant part of my SSH configuration:

Host forge.a-lec.org
  IdentityFile /home/gnutoo/.ssh/projects/libre-en-communs/forges/id_ed25519
  ProxyCommand nc -X 5 -x 127.0.0.1:9050 %h %p
  User git

Host git.a-lec.org
  IdentityFile /home/gnutoo/.ssh/projects/libre-en-communs/forges/id_ed25519
  ProxyCommand nc -X 5 -x 127.0.0.1:9050 %h %p
  User git

I can grep for more things inside if needed (my SSH config has a lot of machines as I try not to share too much the same SSH key to limit the damage if it gets published accidentally in git for instance).

Denis.

Hi, when I push inside a repository I have: <pre> $ git push forgejo HEAD:wip Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 2 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 1022 bytes | 1022.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 remote: remote: To create a merge request for wip, visit: remote: https://git.a-lec.org/GNUtoo/experimental-vms/-/merge_requests/new?merge_request%5Bsource_branch%5D=wip remote: To forge.a-lec.org:GNUtoo/experimental-vms.git f6ee3b7..c8f6259 HEAD -> wip </pre> It pushes to git.a-lec.org and my commit ends up on the gitlab forge. But I used the forge.a-lec.org domain to push: <pre> [gnutoo@primary_laptop experimental-vms]$ git remote get-url forgejo git@forge.a-lec.org:GNUtoo/experimental-vms.git </pre> Here's the relevant part of my SSH configuration: <pre> Host forge.a-lec.org IdentityFile /home/gnutoo/.ssh/projects/libre-en-communs/forges/id_ed25519 ProxyCommand nc -X 5 -x 127.0.0.1:9050 %h %p User git Host git.a-lec.org IdentityFile /home/gnutoo/.ssh/projects/libre-en-communs/forges/id_ed25519 ProxyCommand nc -X 5 -x 127.0.0.1:9050 %h %p User git </pre> I can grep for more things inside if needed (my SSH config has a lot of machines as I try not to share too much the same SSH key to limit the damage if it gets published accidentally in git for instance). Denis.

GNUtoo commented

2023-10-16 19:28:51 +02:00

Author

Member

Comme prévu en réunion et rappelé par Neox ce bogue sera résolu avec la disparition de git.a-lec.org