Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5489

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

git push generated error when the repository had been moved inside a group

Closed

git push generated error when the repository had been moved inside a group

Created by: sumitag

I created a repository, set up the remote on git. I then moved the repository into a group from the admin page. While pushing from git I got "remote end hung up unexpectedly" error.

I would expect this to be handled more gracefully with a error stating remote doesn't exist.

Linked issues
0


  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: animedbz16

    Did you update the git remote origin in your local repository?

    To list remote repos: git remote -v

    If this doesn't match the correct group then you are attempting to push the repo to the old path, which won't exist.

    This would need to be updated.

    By Administrator on 2013-10-30T21:47:32 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: sumitag

    Once I updated the local git it did work. I raised the issue as the error reported was "remote end hung up unexpectedly" shouldn't this be handled properly?

    By Administrator on 2013-10-30T22:35:11 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: mmonge

    This is not a GitLab Issue, it's how Git works on GitHub, GitLab, Bitbucket... you can not expect that it shows you a message about you moving repos to another group. When you do the move action on GitLab it saids you about fixing the remotes.

    By Administrator on 2013-11-05T19:33:03 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
Assign to
Milestone
No milestone
None
None
Time tracking
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
participants
Reference:

Menu

Projects Groups Snippets
Help