Allow ssh info command to list repositories available #3

New Issue

lunny · 2018-11-25T18:39:47Z

lunny commented

2018-11-25 18:39:47 +00:00

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)

lunny commented

2018-11-26 01:12:47 +00:00

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`.

lunny commented

2019-04-15 07:12:31 +00:00

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

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

lunny commented

2019-04-15 20:57:56 +00:00

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.

What do you think about that code?
Which additional information should be listed by default?
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?

lunny commented

2019-05-06 17:01:38 +00:00

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.

root360-AndreasUlm commented

2019-09-13 17:33:58 +00:00

created PR #44

created PR https://gitea.com/gitea/tea/pulls/44

~~6543 referenced this issue 2019-11-03 04:29:58 +00:00~~

add repos subcommand [continue #44] (#3) #65

~~6543 referenced this issue 2019-11-03 04:30:11 +00:00~~

add repos subcommand [continue #44] (#3) #65

6543 referenced this issue

2019-11-03 05:22:06 +00:00

add repos subcommand [continue #44] (#3) #65

lunny referenced this issue from a commit