tea releases create gives error "You have to indicate a repo or execute the command in a repo" but no repo option allowed #12

Closed
opened 2019-04-15 16:09:09 +00:00 by lunny · 6 comments
Owner

Author: @LittleColin

I'm probably doing something stupid but I've successfully done a tea login and was then attempting to create a release with:

tea releases create --title "0.0.1-alpha" --target master --draft --asset myapp.zip

But how do I specify the repo? There is no -r/--repo flag on this command and the preceding login command didn't allow me to specify a repo at the end of the url.

I understandably get the error:
You have to indicate a repo or execute the command in a repo

I'm not sure what "in a repo" means - I'm in the git folder containing my app. Eventually I'll want to do this from the CI.

Any examples of creating a release much appreciated.

FWIW Doing a tea -v gives Tea version 0.1.0-dev

Author: @LittleColin I'm probably doing something stupid but I've successfully done a tea login and was then attempting to create a release with: tea releases create --title "0.0.1-alpha" --target master --draft --asset myapp.zip But how do I specify the repo? There is no -r/--repo flag on this command and the preceding login command didn't allow me to specify a repo at the end of the url. I understandably get the error: `You have to indicate a repo or execute the command in a repo` I'm not sure what "in a repo" means - I'm in the git folder containing my app. Eventually I'll want to do this from the CI. Any examples of creating a release much appreciated. FWIW Doing a tea -v gives _Tea version 0.1.0-dev_
Author
Owner

Author: @techknowlogick

There should be a -r flag in use, per https://github.com/go-gitea/tea/blob/master/cmd/releases.go#L33

Could you try:
tea releases create --title "0.0.1-alpha" --target master --draft --asset myapp.zip -r exampleuser/examplerepo (assuming your username is exampleuser and repo name is examplerepo).

Please respond with updates on success (or otherwise).

Edit: Just saw your edit re: CI, if you use Drone then you can use the following plugin http://plugins.drone.io/drone-plugins/drone-gitea-release/ to create releases and upload attachments

Author: @techknowlogick There should be a `-r` flag in use, per https://github.com/go-gitea/tea/blob/master/cmd/releases.go#L33 Could you try: `tea releases create --title "0.0.1-alpha" --target master --draft --asset myapp.zip -r exampleuser/examplerepo` (assuming your username is `exampleuser` and repo name is `examplerepo`). Please respond with updates on success (or otherwise). Edit: Just saw your edit re: CI, if you use Drone then you can use the following plugin http://plugins.drone.io/drone-plugins/drone-gitea-release/ to create releases and upload attachments
Author
Owner

Author: @LittleColin

-r gives:
Failed to run app with %s: %v[C:\Users\<me>\go\bin\tea.exe releases create --title 0.0.1-alpha --target master --draft --asset myapp.zip -r myorg/myrepo] flag provided but not defined: -r

Author: @LittleColin -r gives: `Failed to run app with %s: %v[C:\Users\<me>\go\bin\tea.exe releases create --title 0.0.1-alpha --target master --draft --asset myapp.zip -r myorg/myrepo] flag provided but not defined: -r`
Author
Owner

Author: @lunny

@LittleColin just do that on your repo git directory.

Author: @lunny @LittleColin just do that on your repo git directory.
Author
Owner

Author: @root360-AndreasUlm

@LittleColin currently --repo is an argument of 'release' thus you have to run tea releases --repo exampleuser/examplerepo create --title "0.0.1-alpha" --target master --draft --asset myapp.zip

@lunny this usage is kind of unintuitive I'll create a PR that adds --repo to the create subcommand

Author: @root360-AndreasUlm @LittleColin currently --repo is an argument of 'release' thus you have to run `tea releases --repo exampleuser/examplerepo create --title "0.0.1-alpha" --target master --draft --asset myapp.zip` @lunny this usage is kind of unintuitive I'll create a PR that adds --repo to the create subcommand
6543 added the
status/needs-feedback
kind/bug
labels 2019-11-08 03:27:05 +00:00
Owner

Is it fixed ...?

Is it fixed ...?
Member

Yes, can be closed. Followup is #57

Yes, can be closed. Followup is #57
6543 closed this issue 2020-01-06 11:52:31 +00:00
6543 removed the
kind/bug
status/needs-feedback
labels 2020-01-06 11:52:37 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#12
No description provided.