Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessive information about repository types #4071

Closed
exalate-issue-sync bot opened this issue Aug 12, 2024 · 0 comments · Fixed by #4088
Closed

Excessive information about repository types #4071

exalate-issue-sync bot opened this issue Aug 12, 2024 · 0 comments · Fixed by #4088
Assignees
Labels
group/backend Issue related to the backend (API Server, Git Agent)

Comments

@exalate-issue-sync
Copy link

h3. As a user

I want to think in terms of repositories and not have to care about the type of repository or where it is stored
So that the menu’s and navigation is easier and focused on actions without exposing too much of Infrahub’s internals

h3. Description

Currently, the sidebar menu has options for both Repository and Read-Only repository. This part could instead be done with a Generic so that we only have one repository item.

h3. Acceptance Criteria

When a user visits the menu of Infrahub. Then only one repository option is present, options are instead presented when creating a repository.

@exalate-issue-sync exalate-issue-sync bot added group/backend Issue related to the backend (API Server, Git Agent) state/planned This issue is planned to be worked on in an upcoming release. labels Aug 12, 2024
@exalate-issue-sync exalate-issue-sync bot added this to the Infrahub - 0.16 milestone Aug 12, 2024
@exalate-issue-sync exalate-issue-sync bot removed the state/planned This issue is planned to be worked on in an upcoming release. label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
group/backend Issue related to the backend (API Server, Git Agent)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant