github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Download Release Attachment via API #8539

New Issue
Open
opened 2025-11-02 08:10:15 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 08:10:15 -06:00
Owner
Copy Link

Originally created by @noetzold on GitHub (Feb 10, 2022).

Feature Description

When using the API to download release attachment via /repos/{owner}/{repo}/releases/{id}/assets/{attachment_id} a download link is provided. But downloading requires login. So, the use of this API call is verry limited. Is would be nice to have a way downloading the attachment with an access token.

Screenshots

No response

Originally created by @noetzold on GitHub (Feb 10, 2022). ### Feature Description When using the API to download release attachment via /repos/{owner}/{repo}/releases/{id}/assets/{attachment_id} a download link is provided. But downloading requires login. So, the use of this API call is verry limited. Is would be nice to have a way downloading the attachment with an access token. ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 08:10:15 -06:00
GiteaMirror commented 2025-11-02 08:10:16 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Feb 10, 2022):

https://try.gitea.io/api/swagger#/repository/repoGetReleaseAttachment

@6543 commented on GitHub (Feb 10, 2022): https://try.gitea.io/api/swagger#/repository/repoGetReleaseAttachment
GiteaMirror commented 2025-11-02 08:10:16 -06:00
Author
Owner
Copy Link

@noetzold commented on GitHub (Feb 10, 2022):

Yes, this is the API call returning a “browser_download_url”
For example:
https://try.gitea.io/api/v1/repos/fnetx/testing-gitea-releases/releases/3318489/assets/2114?access_token=12345
"browser_download_url": "https://try.gitea.io/attachments/f505c259-0ccf-4b66-893d-1f4880f236aa"

But when using authorization a login with user/password is required for downloading the file.

@noetzold commented on GitHub (Feb 10, 2022): Yes, this is the API call returning a “browser_download_url” For example: https://try.gitea.io/api/v1/repos/fnetx/testing-gitea-releases/releases/3318489/assets/2114?access_token=12345 "browser_download_url": "https://try.gitea.io/attachments/f505c259-0ccf-4b66-893d-1f4880f236aa" But when using authorization a login with user/password is required for downloading the file.
GiteaMirror commented 2025-11-02 08:10:16 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Feb 10, 2022):

well either add token auth to this endpoint or add a new endpoint ...

@6543 commented on GitHub (Feb 10, 2022): well either add token auth to this endpoint or add a new endpoint ...
GiteaMirror commented 2025-11-02 08:10:16 -06:00
Author
Owner
Copy Link

@ajtuma commented on GitHub (Aug 22, 2023):

A new endpoint... Could you please explain it more widely?

@ajtuma commented on GitHub (Aug 22, 2023): A new endpoint... Could you please explain it more widely?
GiteaMirror commented 2025-11-02 08:10:17 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 22, 2023):

#26430 should fix this issue.

@lunny commented on GitHub (Aug 22, 2023): #26430 should fix this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8539
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?