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

Adopt repository case errors #6654

New Issue
Closed
opened 2025-11-02 07:02:39 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 07:02:39 -06:00
Owner
Copy Link

Originally created by @LukeMauldin on GitHub (Jan 7, 2021).

  • Gitea version (or commit ref): 1.13.0 - downloaded from Github release, running via systemd
  • Git version: 2.27
  • Operating system: RHEL 8.3
  • Database (use [x]):
    • [ X ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • [ X ] No

Description

When using the Adopt repository functionality I have run into 2 bugs.

  1. When the repository name is mixed case, it does not show up on the "Adopt Repositories" web page and it will not work via the API. Example: If the repository is named: /var/lib/gitea/repos/archive/TestRepo/, it will not show up on the web page and not work via the API. If the repository is named /var/lib/gitea/repos/archive/testrepo/then the adoption functionality will work as expected. A work-around is to name the repository as lower-case for the import and then do an API call to update the name to mixed case.
  2. When the organization name is mixed case, it does show up on the "Adopt Repositories" web page but the Adopt fails without an error and refreshes the screen. Also, it will not work via the API. Example: If the repository is named /var/lib/gitea/repos/Archive/testrepo/, it will show up on the web page but the Adopt will not work and the API will not work. There is no practical work-around for this issue except to have all organizations named lower case but that would break other applications that depend on the correct casing.
Originally created by @LukeMauldin on GitHub (Jan 7, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.13.0 - downloaded from Github release, running via systemd - Git version: 2.27 - Operating system: RHEL 8.3 - Database (use `[x]`): - [ X ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ X ] No ## Description When using the Adopt repository functionality I have run into 2 bugs. 1) When the repository name is mixed case, it does not show up on the "Adopt Repositories" web page and it will not work via the API. Example: If the repository is named: `/var/lib/gitea/repos/archive/TestRepo/`, it will not show up on the web page and not work via the API. If the repository is named `/var/lib/gitea/repos/archive/testrepo/`then the adoption functionality will work as expected. A work-around is to name the repository as lower-case for the import and then do an API call to update the name to mixed case. 2) When the organization name is mixed case, it does show up on the "Adopt Repositories" web page but the Adopt fails without an error and refreshes the screen. Also, it will not work via the API. Example: If the repository is named `/var/lib/gitea/repos/Archive/testrepo/`, it will show up on the web page but the Adopt will not work and the API will not work. There is no practical work-around for this issue except to have all organizations named lower case but that would break other applications that depend on the correct casing.
GiteaMirror added the issue/not-a-bug label 2025-11-02 07:02:39 -06:00
GiteaMirror commented 2025-11-02 07:02:40 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 7, 2021):

That is because Gitea does not and will not create repositories with capitals in their folder names.

@zeripath commented on GitHub (Jan 7, 2021): That is because Gitea does not and will not create repositories with capitals in their folder names.
GiteaMirror commented 2025-11-02 07:02:41 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 7, 2021):

And the repo is suppose to be a bare repo like testrepo.git

@zeripath commented on GitHub (Jan 7, 2021): And the repo is suppose to be a bare repo like testrepo.git
GiteaMirror commented 2025-11-02 07:02:44 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 7, 2021):

Gitea's repos are meant to be Gitea's alone - it is not intended that other applications are to be allowed to use its repos without deep understanding of how Gitea uses its repos.

@zeripath commented on GitHub (Jan 7, 2021): Gitea's repos are meant to be Gitea's alone - it is not intended that other applications are to be allowed to use its repos without deep understanding of how Gitea uses its repos.
GiteaMirror commented 2025-11-02 07:02:45 -06:00
Author
Owner
Copy Link

@LukeMauldin commented on GitHub (Jan 10, 2021):

By using lower case organization and repository names I was able to work around the errors I was getting previously.

@LukeMauldin commented on GitHub (Jan 10, 2021): By using lower case organization and repository names I was able to work around the errors I was getting previously.
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 issue/not-a-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#6654
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?