Request for Granular Folder-Level Access Control in Github #102755
Unanswered
rakibulalam
asked this question in
Code Security
Replies: 1 comment 5 replies
-
You can limit write access by setting branch protection rules. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
General
Body
I am writing to highlight a significant challenge faced by developers working on projects that use a mono-repository framework to manage microservices, frontend and backend applications. The current lack of granular folder-level access control within these mono repositories creates security and access management issues for development teams.
Problem Statement:
With the growing trend towards mono repositories for managing microservices, frontend and backend applications, developers often find themselves working on projects with a unified codebase. While this approach has many advantages, it also presents challenges related to access control. Currently, developers with access to the Mono repository gain visibility and access to all folders, including microservices, frontend, and backend applications.
Problems encountered:
Security concerns: Housing of different services in mono repositories, lack of fine-grained access control at the folder level poses risk of unintended access to sensitive code and data.
Access Management: With multiple teams responsible for different services within a mono repository, managing access permissions becomes complex. Developers may have wider access than necessary, leading to potential security vulnerabilities.
Codebase clutter: In large mono repositories, the presence of multiple services can lead to codebase clutter. Developers may inadvertently interact with or modify code outside of their designated area.
Suggested solution:
I urge GitHub to consider implementing a feature that allows for granular folder-level access control within Mono repositories. This enhancement will enable developers to set permissions at the folder level, ensuring that each team or developer has access to specific parts of the codebase related to their responsibilities.
Use Cases:
Microservices: Developers working on a specific microservice should only have access to folders and code related to that specific microservice.
Separation of frontend and backend: Teams responsible for frontend and backend applications may have separate access permissions to maintain separation of concerns.
Enhanced security: Folder-level access control supports a more secure development environment, reducing the risk of unintended access to sensitive information.
I believe that including folder-level access control in Mono repositories will significantly increase the manageability and security of projects following this architecture. I appreciate GitHub's commitment to continuous improvement and innovation, and I look forward to any updates on this.
Beta Was this translation helpful? Give feedback.
All reactions