RepoOption -r allow more variants #163

New Issue

6543 · 2020-07-19T16:17:05Z

6543 commented

2020-07-19 16:17:05 +00:00

currently -r only allow path to local git repos with remotes's to a gitea instance

make it posible to specify gitea repos with no local related git repo

if the -r argument does not match a local existing path ...

... if format is '\w+/\w+' -> split by '/', first is owner second is repo

... if format is '\w+' -> owner is current user repo is arguemnt

currently -r only allow path to local git repos with remotes's to a gitea instance make it posible to specify gitea repos with no local related git repo if the -r argument does not match a local existing path ... ... if format is '\w+/\w+' -> split by '/', first is owner second is repo ... if format is '\w+' -> owner is current user repo is arguemnt

6543 added the

kind/proposal

label 2020-07-19 16:19:50 +00:00

6543 added

kind

feature

and removed

kind/proposal

labels 2020-07-19 20:43:14 +00:00

6543 added the

priority/high

label 2020-07-19 20:44:20 +00:00

6543 added this to the v0.5.0 milestone 2020-07-19 20:44:23 +00:00

noerw commented

2020-08-28 08:11:53 +00:00

In what kind of workflow would it be useful to keep the current beheviour with local paths?
I'd just completely replace it with the <owner>/<repo> variant, which is more predictable, and avoids having multiple syntaxes.

When you're in the situation of creating a PR, you're probably thinking about which owner & repo it should go to, and not where you have it locally on your device anyway.

(Also: standard workflows add upstreams/forks as remotes, not separate repos.. Not sure why such a workflow should be supported by tea)

#169 related

In what kind of workflow would it be useful to keep the current beheviour with local paths? I'd just completely replace it with the `<owner>/<repo>` variant, which is more predictable, and avoids having multiple syntaxes. When you're in the situation of creating a PR, you're probably thinking about which owner & repo it should go to, and not where you have it locally on your device anyway. (Also: standard workflows add upstreams/forks as remotes, not separate repos.. Not sure why such a workflow should be supported by tea) #169 related

👍 1

6543 referenced a pull request that will close this issue

2020-09-14 01:11:40 +00:00

More Options To Specify Repo #178

6543 added the

status/has-pull

label 2020-09-15 21:08:34 +00:00

6543 closed this issue

2020-09-16 13:47:55 +00:00

6543 referenced this issue from a commit

2020-09-16 13:47:55 +00:00

More Options To Specify Repo (#178)