go-gitea/tea
1
0
Fork 0
mirror of https://github.com/go-gitea/tea.git synced 2026-07-01 21:03:59 -04:00
Code Issues 9 Packages Projects Releases Wiki Activity

[GH-ISSUE #4] support tea releases create with asset upload #1

New Issue
Closed
opened 2026-02-16 12:57:45 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 12:57:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @noerw on GitHub (Dec 3, 2018).
Original GitHub issue: https://github.com/go-gitea/tea/issues/4

I'm happy to provide a pull request implementing this functionality, but want to find consensus on the command line interface first.

I'd prefer a command like this:

tea releases create --tag v1.0 --target master -t v1.0 --asset artifact1.zip --asset artifact2

But I saw that in the HTTP API assets are handled in a separate endpoint. Would the API described above be fine anyway?

Originally created by @noerw on GitHub (Dec 3, 2018). Original GitHub issue: https://github.com/go-gitea/tea/issues/4 I'm happy to provide a pull request implementing this functionality, but want to find consensus on the command line interface first. I'd prefer a command like this: ``` tea releases create --tag v1.0 --target master -t v1.0 --asset artifact1.zip --asset artifact2 ``` But I saw that in the HTTP API assets are handled in a separate endpoint. Would the API described above be fine anyway?
yindo closed this issue 2026-02-16 12:57:45 -05:00
yindo commented 2026-02-16 12:57:46 -05:00
Author
Owner
Copy Link
Copy Source

@lunny commented on GitHub (Dec 3, 2018):

Please send your pull request, maintainers will review it.

@lunny commented on GitHub (Dec 3, 2018): Please send your pull request, maintainers will review it.
yindo commented 2026-02-16 12:57:46 -05:00
Author
Owner
Copy Link
Copy Source

@simbo1905 commented on GitHub (Dec 31, 2018):

The GitHub CLI hub release might provide some inspiration as to what the api could look like. For example you are suggesting creation a release from master which is a moving target; someone might push a broken commit just at the instance you are releasing. So the hub tool takes a “commitish” as the target such as a sha hash for a commit. By taking inspiration from that mature tool it will make it easier for people to write release automation scripts that are easy to migrate from other git servers onto gitea.

@simbo1905 commented on GitHub (Dec 31, 2018): The GitHub CLI [hub release](https://hub.github.com/hub-release.1.html) might provide some inspiration as to what the api could look like. For example you are suggesting creation a release from master which is a moving target; someone might push a broken commit just at the instance you are releasing. So the hub tool takes a “commitish” as the target such as a sha hash for a commit. By taking inspiration from that mature tool it will make it easier for people to write release automation scripts that are easy to migrate from other git servers onto gitea.
yindo commented 2026-02-16 12:57:46 -05:00
Author
Owner
Copy Link
Copy Source

@noerw commented on GitHub (Mar 11, 2019):

was implemented with #6

@noerw commented on GitHub (Mar 11, 2019): was implemented with #6
yindo changed title from support `tea releases create` with asset upload to [GH-ISSUE #4] support `tea releases create` with asset upload 2026-06-05 16:34:03 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
kind/build
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: go-gitea/tea#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?