gogs / gogs/gogs

Transferring ownership of private repository

Open
#2,656 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

💊 bug 🔨 enhancement 🙇‍♂️ help wanted
Dominant language
Go
Stars
47.8k
Forks
5.1k
Avg merge
7h 23m
Merged PRs (30d)
5

Description

Gogs Info

  • Gogs version (or commit ref): 0.8.31.0205
  • Git version: 2.1.4
  • Operating system: Debian 8.3
  • Database:
    • PostgreSQL
    • MySQL
    • SQLite
  • Log gist:

Description

Assume the following:

  • I have a Organization called "Org" with two Teams: "Owner" and "Admin Access".
  • "User" is member of "Org" and "Admin Access".

Now, "User" creates a private repository as "User/Repo". Afterwards he transfers ownership to Org/Repo. "User" cannot see the repository anymore or add it to the team "Admin Access". Only members of the team "Owner" can add the repository to the team "Admin Access".

Expected Behaviour

I would suggest, that "User" should still be able to add the repository to the Team "Admin Access".
Alternatively, a warning that only users with owner rights can handle the repository would be sufficient: The warning "Transfer this repository to another user or to an organization in which you have admin rights" seems to be incorrect.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the private-repository transfer from a user to an organization, then trace the repository and team permission handling described in the issue. Compare the resulting access and team-management behavior with the two proposed outcomes: retaining the user's ability to add the repository, or showing an accurate warning before transfer.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, mysql
Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.