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

transfer of repos allowed from users not in an organizations team. #1999

New Issue
Open
opened 2025-11-02 04:20:39 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 04:20:39 -06:00
Owner
Copy Link

Originally created by @haai on GitHub (Jul 2, 2018).

  • Gitea version (or commit ref):
    1.4.2+6-gcaee487
  • Git version:
    1.4.2+6-gcaee487
  • Operating system:
    CoreOS + Docker
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Have an organization testorg created. repos are private per default.
Create an testuser NOT member of the organization testorg.
Create a Repo under testuser (testuser/testrepo)
Transfer ownership of repo testuser/testrepo to organization testorg.

Actual behaviour:

The transfer of the ownership is successful and leads to the project site with 404 page.

Expected behaviour:

The ownership transfer fails because the testuser is in no team nor admin.

Is this a bug or feature? :)
...

Screenshots

none

Originally created by @haai on GitHub (Jul 2, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. 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.4.2+6-gcaee487 - Git version: 1.4.2+6-gcaee487 - Operating system: CoreOS + Docker - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Have an organization `testorg` created. repos are private per default. Create an `testuser` NOT member of the organization `testorg`. Create a Repo under `testuser` (`testuser/testrepo`) Transfer ownership of repo `testuser/testrepo` to organization `testorg`. ### Actual behaviour: The transfer of the ownership is successful and leads to the project site with 404 page. ### Expected behaviour: The ownership transfer fails because the testuser is in no team nor admin. Is this a bug or feature? :) ... ## Screenshots none
GiteaMirror added the issue/confirmedtype/feature labels 2025-11-02 04:20:39 -06:00
GiteaMirror commented 2025-11-02 04:20:40 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Jul 2, 2018):

I think we should implement a sort of request workflow. It should be possible to transfer a repo to another org without being member.

@jonasfranz commented on GitHub (Jul 2, 2018): I think we should implement a sort of request workflow. It should be possible to transfer a repo to another org without being member.
GiteaMirror commented 2025-11-02 04:20:40 -06:00
Author
Owner
Copy Link

@haai commented on GitHub (Jul 3, 2018):

could you clarify why it should be possible?

@haai commented on GitHub (Jul 3, 2018): could you clarify why it should be possible?
GiteaMirror commented 2025-11-02 04:20:41 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Jul 7, 2018):

Example I am contributor of a project at gitea but not member of the project's organization. If I want to transfer a repo to the project's repo, I should need to send an request for that. This makes it simpler to contribute by adding repos.

@jonasfranz commented on GitHub (Jul 7, 2018): Example I am contributor of a project at gitea but not member of the project's organization. If I want to transfer a repo to the project's repo, I should need to send an request for that. This makes it simpler to contribute by adding repos.
GiteaMirror commented 2025-11-02 04:20:41 -06:00
Author
Owner
Copy Link

@haai commented on GitHub (Jul 9, 2018):

ah ok i misinterpreted your answer :) i am all yours.

@haai commented on GitHub (Jul 9, 2018): ah ok i misinterpreted your answer :) i am all yours.
GiteaMirror commented 2025-11-02 04:20:41 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 19, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 19, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:20:41 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Jan 19, 2019):

I’m working on a transfer workflow at https://github.com/go-gitea/gitea/issues/5744

@adelowo commented on GitHub (Jan 19, 2019): I’m working on a transfer workflow at https://github.com/go-gitea/gitea/issues/5744
GiteaMirror commented 2025-11-02 04:20:42 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 20, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 20, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
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/confirmed type/feature
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#1999
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?