Allow ssh info command to list repositories available #3

Closed
opened 4 years ago by lunny · 5 comments
lunny commented 4 years ago
Owner

Author: @xdch47

Certain other repository management tools, such as Gitolite, allow a user to see what repositories they have access to by passing info to the SSH command.

For example, ssh git@git.gitea.io info

The result is a list of repositories.

This is really useful not only for command-line users but also for quickly verifying what access someone has.

Could Gitea support this?

(Moved from https://github.com/go-gitea/gitea/issues/5124)

Author: @xdch47 Certain other repository management tools, such as Gitolite, allow a user to see what repositories they have access to by passing info to the SSH command. For example, ssh git@git.gitea.io info The result is a list of repositories. This is really useful not only for command-line users but also for quickly verifying what access someone has. Could Gitea support this? (Moved from https://github.com/go-gitea/gitea/issues/5124)
Poster
Owner

Author: @lunny

I think we can implement both tea repos and ssh git@gitea.gitea.io info.

Author: @lunny I think we can implement both `tea repos` and `ssh git@gitea.gitea.io info`.
Poster
Owner

Author: @root360-AndreasUlm

Hi,

I'd like to work on the feature to manage repositories as we want to use 'tea' in our company to managed repositories.

My initial focus would be listing of repositories.
The following features for listing are currently on my roadmap:

  1. Do you see any issues with this initial roadmap?

Regards,
Andreas

Author: @root360-AndreasUlm Hi, I'd like to work on the feature to manage repositories as we want to use 'tea' in our company to managed repositories. My initial focus would be listing of repositories. The following features for listing are currently on my roadmap: - by default list all repositories that are found by https://godoc.org/code.gitea.io/sdk/gitea#Client.ListMyRepos - add '--mode' to filter with available modes "fork", "source", “mirror” and “collaborative” (like https://try.gitea.io/api/swagger#/repository/repoSearch) - add '--org' to filter based on organization - add '--user' to filter based on user 1) Do you see any issues with this initial roadmap? Regards, Andreas
Poster
Owner

Author: @root360-AndreasUlm

I created an initial pull request with the ability to list all repositories the provided login has access to.
Currently it is printing repo-fullname, repo-mode, repo-SSH-URL and repo-owner-username.

  1. What do you think about that code?
  2. Which additional information should be listed by default?
  3. Should I maybe implement an argument that give control over the printed columns?
Author: @root360-AndreasUlm I created an initial pull request with the ability to list all repositories the provided login has access to. Currently it is printing repo-fullname, repo-mode, repo-SSH-URL and repo-owner-username. 1) What do you think about that code? 2) Which additional information should be listed by default? 3) Should I maybe implement an argument that give control over the printed columns?
Poster
Owner

Author: @root360-AndreasUlm

I implemented the filter flags into the list subcommand.
The main command 'tea repo' does not allow filtering but list all repos visible to the running user.

Author: @root360-AndreasUlm I implemented the filter flags into the list subcommand. The main command 'tea repo' does not allow filtering but list all repos visible to the running user.

created PR #44

created PR https://gitea.com/gitea/tea/pulls/44
6543 closed this issue 3 years ago
Sign in to join this conversation.
Loading…
There is no content yet.