Skip to content

GitLab

  • Menu
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
  • #3033

Closed
Open
Created Feb 19, 2013 by Administrator@rootOwner

Moving a project to a new namespace doesn't send the right git remote URI in the email

Created by: alexrussell

I just moved a project from my personal namespace to a new Group I created, and it worked fine. Going into the project I can see the new git remote URL but I also got an email saying my project had changed its location. The helpful git remote set-url command in the email still had the old git URL.

I'm using branch 4-1-stable at commit 0ac9dd32.

Unfortunately I can't quite debug exactly where it's going wrong. (I'm not a Ruby/Rails developer.) It looks like the code's doing everything right though. The Project after_update observer checks if the namespace changed, if so calls send_move_instructions which simply passes the Project model to the email, which then uses project.ssh_url_to_repo to get the URL to send in the email. Maybe it's a bug in the underlying framework - url_to_repo has stale data?

Assignee
Assign to
Time tracking