Closed lachmanfrantisek closed 6 years ago
There is only a problem with the descriptions -- the GitHub API does return them...
Subcommand split:
$ tool list-labels --help
Usage: tool list-labels [OPTIONS] [REPO]
List labels for the project. This is how you can select a repository for
Github: <namespace>/<project>.
Options:
-s, --service TEXT Name of the git service (e.g. github/gitlab).
--help Show this message and exit.
$ tool update-labels --help
Usage: tool update-labels [OPTIONS] DESTINATION [SOURCE]
Update labels of other project. Multiple destinations can be set by
joining them with semicolon. This is how you can select a repository for
Github: <namespace>/<project>.
Options:
-s, --service TEXT Name of the git service for destination (e.g.
github/gitlab).
--source-service TEXT Name of the git service (e.g. github/gitlab).
--help Show this message and exit.
@TomasTomecek I have two questions:
$ tool update-labels user-cont/colin\;user-cont/conu user-cont/tool
REPO
argument in other commands? Is the destination
ok?Thanks.
I've also added support for the gitlab. Some notes about that:
#
at the start). --> Currently, I am converting the colours on the update. Does it make sense to use some common format for list-labels
?--source-service
to allow different service for the source and destination. (If there are multiple destinations, all will have the same service.) Any idea to achieve multiple destinations than this:
$ tool update-labels user-cont/colin\;user-cont/conu user-cont/tool
how about $ tool update-labels --source-repo https://github.com/user-cont/kwaciaren user-cont/x user-cont/y
. --source-repo
would default to repo in PWD.
Do we need to be consistent with the REPO argument in other commands? Is the destination ok?
Yes, that's fine. I'm working on configuration PR and let's discuss over there once I open it.
The colour format differ (Github does not have # at the start). --> Currently, I am converting the colours on the update. Does it make sense to use some common format for list-labels?
Personally, I don't care.
I've added --source-service to allow different service for the source and destination. (If there are multiple destinations, all will have the same service.)
This is pretty nuts!
@TomasTomecek I've done as you wrote...
Well done!