Problem Statement
Currently, the app only supports public repositories. This limits its usefulness for users who work primarily with private repositories, which is very common in professional or commercial projects. Many teams rely on private repos for internal development, and without support for them, the app cannot be fully integrated into real-world workflows.
Proposed Solution
Allow users to connect a project to one or multiple repositories by signing in with their GitHub account. After authentication (via GitHub OAuth or support multiple version control vendors), users should be able to:
- Grant the necessary permissions (including access to private repositories).
- Select one or multiple repositories from their account.
- Link those repositories directly to their project inside the app.
This would enable secure and seamless access to both public and private repositories the user has permission to view.
Alternative Solutions
- Allow users to manually provide a Personal Access Token (PAT) with the required scopes.
- Support repository access through a backend integration where users configure repository access manually.
- Initially support private repositories only for organization accounts.
Relevant Context
Many developers manage multiple repositories per project (e.g., frontend, backend, infrastructure). Supporting multi-repository linking via GitHub sign-in would make the app much more flexible and practical for real-world use cases.
Does this feature align with Kaneo's focus on simplicity?
Yes, because GitHub sign-in provides a familiar and streamlined authentication flow. Allowing users to select repositories directly from their account keeps the experience intuitive while expanding the app’s capabilities without adding unnecessary complexity.
Problem Statement
Currently, the app only supports public repositories. This limits its usefulness for users who work primarily with private repositories, which is very common in professional or commercial projects. Many teams rely on private repos for internal development, and without support for them, the app cannot be fully integrated into real-world workflows.
Proposed Solution
Allow users to connect a project to one or multiple repositories by signing in with their GitHub account. After authentication (via GitHub OAuth or support multiple version control vendors), users should be able to:
This would enable secure and seamless access to both public and private repositories the user has permission to view.
Alternative Solutions
Relevant Context
Many developers manage multiple repositories per project (e.g., frontend, backend, infrastructure). Supporting multi-repository linking via GitHub sign-in would make the app much more flexible and practical for real-world use cases.
Does this feature align with Kaneo's focus on simplicity?
Yes, because GitHub sign-in provides a familiar and streamlined authentication flow. Allowing users to select repositories directly from their account keeps the experience intuitive while expanding the app’s capabilities without adding unnecessary complexity.