Skip to content

Add API Support to Download Artifacts from Actions #32124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MrDiba opened this issue Sep 24, 2024 · 0 comments · Fixed by #33510
Closed

Add API Support to Download Artifacts from Actions #32124

MrDiba opened this issue Sep 24, 2024 · 0 comments · Fixed by #33510
Labels
topic/api Concerns mainly the API topic/gitea-actions related to the actions of Gitea type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@MrDiba
Copy link

MrDiba commented Sep 24, 2024

Feature Description

As far as I know, currently, the Gitea API does not provide a direct method to download artifacts generated by Gitea Actions (using actions/upload-artifact). This feature request proposes adding an endpoint that enables users to download workflow artifacts via the API.

In the webbrowser the /repos/{owner}/{repo}/actions/runs/{run_id}/artifacts endpoint is available and I'm able to download the artifact using curl by first getting an cookie and then by using the cookie to get the artifact. But I think it would be better to directly use the API with token authentication.

Screenshots

No response

@MrDiba MrDiba added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Sep 24, 2024
@lunny lunny added the topic/gitea-actions related to the actions of Gitea label Sep 24, 2024
@techknowlogick techknowlogick added the topic/api Concerns mainly the API label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/api Concerns mainly the API topic/gitea-actions related to the actions of Gitea type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants