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

Name change #11163

New Issue
Closed
opened 2025-11-02 09:29:27 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 09:29:27 -06:00
Owner
Copy Link

Originally created by @C-EO on GitHub (Jul 4, 2023).

Description

I have tried to change the name of my repo under an organization and Gitea keeps telling me The repository name is already used. I have tried checking for an available repo using the URL, but it returns the 404 page.

Is it a problem with the DB I'm using or?
( I use MySQL from Planetscale)

Gitea Version

1.21.0+dev-215-gff140d405

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

image

image

https://github.com/go-gitea/gitea/assets/85847352/83b9e971-6fe9-4fb8-ad8b-c8e7d7aaafe5

Git Version

2.33.1, Wire Protocol Version 2 Enabled

Operating System

linux 5.19.0-1026-gcp

How are you running Gitea?

I'm using a binary download from here. I' running Gitea from the command-line with a GUI.

Database

MySQL

Originally created by @C-EO on GitHub (Jul 4, 2023). ### Description I have tried to change the name of my repo under an organization and Gitea keeps telling me `The repository name is already used.` I have tried checking for an available repo using the URL, but it returns the 404 page. Is it a problem with the DB I'm using or? ( I use MySQL from Planetscale) ### Gitea Version 1.21.0+dev-215-gff140d405 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/85847352/eb0d070b-0c56-4be1-ac5c-41a6eec7fc7a) ![image](https://github.com/go-gitea/gitea/assets/85847352/71a22447-8647-4f53-b500-0d4d1c0ebb30) https://github.com/go-gitea/gitea/assets/85847352/83b9e971-6fe9-4fb8-ad8b-c8e7d7aaafe5 ### Git Version 2.33.1, Wire Protocol Version 2 Enabled ### Operating System linux 5.19.0-1026-gcp ### How are you running Gitea? I'm using a binary download from [here](https://dl.gitea.com/gitea/main/gitea-main-nightly-linux-amd64). I' running Gitea from the command-line with a GUI. ### Database MySQL
GiteaMirror added the type/bug label 2025-11-02 09:29:27 -06:00
GiteaMirror commented 2025-11-02 09:29:28 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Jul 4, 2023):

Maybe this is because there was a previous repo with that name. I do recall we keep some info on renamed repos in the database to be able to redirect the name after a rename. If this blocks the creation, it's a bug.

@silverwind commented on GitHub (Jul 4, 2023): Maybe this is because there was a previous repo with that name. I do recall we keep some info on renamed repos in the database to be able to redirect the name after a rename. If this blocks the creation, it's a bug.
GiteaMirror commented 2025-11-02 09:29:28 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Jul 5, 2023):

Maybe there's previous data in data/gitea-reposiroties/imperialbot/musicbot.git

@yp05327 commented on GitHub (Jul 5, 2023): Maybe there's previous data in `data/gitea-reposiroties/imperialbot/musicbot.git`
GiteaMirror commented 2025-11-02 09:29:28 -06:00
Author
Owner
Copy Link

@C-EO commented on GitHub (Jul 6, 2023):

None exists there

@C-EO commented on GitHub (Jul 6, 2023): None exists there
GiteaMirror commented 2025-11-02 09:29:28 -06:00
Author
Owner
Copy Link

@C-EO commented on GitHub (Jul 6, 2023):

Found it. After reloading the system I found it.

But one question though, which cron-job is supposed to delete empty repos?

I ran all of them but it wasn't until I deleted the musicbot.git myself that I could get to rename.

@C-EO commented on GitHub (Jul 6, 2023): Found it. After reloading the system I found it. But one question though, which cron-job is supposed to delete empty repos? I ran all of them but it wasn't until I deleted the `musicbot.git` myself that I could get to rename.
GiteaMirror commented 2025-11-02 09:29:29 -06:00
Author
Owner
Copy Link

@denyskon commented on GitHub (Oct 27, 2023):

Is this issue solved?

@denyskon commented on GitHub (Oct 27, 2023): Is this issue solved?
GiteaMirror commented 2025-11-02 09:29:29 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Oct 30, 2023):

At least the original issue seems to have turned out invalid.

@silverwind commented on GitHub (Oct 30, 2023): At least the original issue seems to have turned out invalid.
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/bug
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#11163
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?