Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #8935

Closed (moved)
Open
Created Jan 15, 2016 by Justinas Rakašis@dopesong

Forks of private projects should inherit permissions from the parent project

Problem to solve

Private projects can be forked by individuals causing the original project maintainer to lose access and control. This can also prevent merge requests being opened. We should give maintainers of private projects access to forks.

Further details

This would make it possible for the Allow edits by maintainers option to be enabled for Private projects.

This would solve the problem where it isn't possible to access CI pipelines of a private fork.

This is also consistent with GitHub's forking model (https://help.github.com/articles/about-forks/):

Private forks inherit the permissions structure of the upstream or parent repository. For example, if the upstream repository is private and gives read/write access to a team, then the same team will have read/write access to any forks of the private upstream repository. This helps owners of private repositories maintain control over their code.

Proposal

Users and groups with permissions to access a private project, should have the same permissions to access the fork.

Links

  • https://gitlab.com/gitlab-org/gitlab-ce/issues/22292
  • http://feedback.gitlab.com/forums/176466-general/suggestions/5760385-forks-should-inherit-permissions-from-parent-proje
Edited Jul 29, 2019 by James Ramsay (ex-GitLab)
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None