github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-22 05:15:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Incosistency when Repo already exists between create/migrate #3049

New Issue
Closed
opened 2025-11-02 04:58:55 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:58:55 -06:00
Owner
Copy Link

Originally created by @bogdanpetrea on GitHub (Mar 14, 2019).

  • Gitea version (or commit ref): d7542bfde3
  • Git version: 1.7.4
  • Operating system: any
  • Database: any
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

There is an incosistency between handling an RepoAlreadyExists error between migrating a repo and creating a fresh one:

I think the migrating repo error response (409 Conflict, The repository with the same name already exists.) should be used in both cases.

Originally created by @bogdanpetrea on GitHub (Mar 14, 2019). - Gitea version (or commit ref): https://github.com/go-gitea/gitea/commit/d7542bfde3e46b5b11d2296e69f86a0e32ce9565 - Git version: 1.7.4 - Operating system: any - Database: any - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description There is an incosistency between handling an RepoAlreadyExists error between migrating a repo and creating a fresh one: - [migrating repo](https://github.com/go-gitea/gitea/blob/7afe81f28e530c1c5aed1583654b3d772c368fa5/routers/api/v1/repo/repo.go#L412) - [creating fresh repo](https://github.com/go-gitea/gitea/blob/7afe81f28e530c1c5aed1583654b3d772c368fa5/routers/api/v1/repo/repo.go#L232) I think the migrating repo error response (`409 Conflict`, `The repository with the same name already exists.`) should be used in both cases.
GiteaMirror added the type/bugmodifies/api labels 2025-11-02 04:58:55 -06:00
GiteaMirror commented 2025-11-02 04:58:56 -06:00
Author
Owner
Copy Link

@wkulhanek commented on GitHub (Oct 15, 2020):

This 409 is not documented on the /api/swagger. Could it be added, please?

@wkulhanek commented on GitHub (Oct 15, 2020): This 409 is not documented on the /api/swagger. Could it be added, please?
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 modifies/api 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#3049
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?