github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

"Repository name has already been used" when migrating #512

New Issue
Closed
opened 2025-11-02 03:26:16 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 03:26:16 -06:00
Owner
Copy Link

Originally created by @cez81 on GitHub (Mar 15, 2017).

  • Gitea version (or commit ref): 1.1.0+32-g03d7998
  • Git version: 2.7.4
  • Operating system: Ubuntu 16.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io: (currently 404)
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

  1. Start new migration
  2. Enter URL of repo (I used https://github.com/puikinsh/Dazzling.git)
  3. Enter Repository Name same as original repo
  4. Click migrate
  5. Error message saying "Repository name has already been used" even though it doesn't
  6. Repo is still properly migrated

Screenshots

migration

Originally created by @cez81 on GitHub (Mar 15, 2017). - Gitea version (or commit ref): 1.1.0+32-g03d7998 - Git version: 2.7.4 - Operating system: Ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: (currently 404) - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description 1. Start new migration 2. Enter URL of repo (I used https://github.com/puikinsh/Dazzling.git) 3. Enter Repository Name same as original repo 4. Click migrate 5. Error message saying "Repository name has already been used" even though it doesn't 6. Repo is still properly migrated ## Screenshots ![migration](https://cloud.githubusercontent.com/assets/9416498/23974025/6789005c-09d9-11e7-827a-09774a545594.png)
GiteaMirror added the type/question label 2025-11-02 03:26:16 -06:00
GiteaMirror commented 2025-11-02 03:26:17 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 16, 2017):

maybe you can check if there is the same name directory on the your repos directory

@lunny commented on GitHub (Mar 16, 2017): maybe you can check if there is the same name directory on the your repos directory
GiteaMirror commented 2025-11-02 03:26:17 -06:00
Author
Owner
Copy Link

@cez81 commented on GitHub (Mar 16, 2017):

I tried multiple times with different random repos that definately didn't already exist. Can't reproduce on https://try.gitea.io now so might be something with my setup.
Closing this for now.

@cez81 commented on GitHub (Mar 16, 2017): I tried multiple times with different random repos that definately didn't already exist. Can't reproduce on https://try.gitea.io now so might be something with my setup. Closing this for now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#512
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?