actions/upload-artifact

upload-artifact is a GitHub Actions action that uploads workflow artifacts to GitHub's artifact storage system.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):CI/CD & ReleaseDevOps & Observability
Added to GitGenius on September 16th, 2026
Created on June 18th, 2019
Open Issues & Pull Requests: 262 (+0)
GitHub issues: Enabled
Number of forks: 1,099
Total Stargazers: 4,198 (+0)
Total Subscribers: 91 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.9 days
Mean response time: 61.9 days
90th percentile: 191.1 days
Tracked items: 158

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 25% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 129
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 837 days
Stale 30+ days: 108
Stale 90+ days: 91

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 3

Top labels

  • bug (107)
  • enhancement (47)
  • documentation (17)
  • v4 (16)
  • question (4)
  • Artifact Permissions (2)
  • UI (2)
  • invalid (2)

Most active issues this week

Detailed Description

upload-artifact is a GitHub Actions action that uploads workflow artifacts to GitHub's artifact storage system.

The action solves the problem of persisting build outputs and test results across workflow runs by providing a straightforward interface to store files generated during job execution. It works by accepting file paths or glob patterns as input and uploading the specified files to GitHub's artifact backend, internally powered by the @actions/artifact package. Users can upload individual files, entire directories, or sets of files matching wildcard patterns, with options to control compression levels and retention periods.

Teams should adopt this action if they need to preserve workflow outputs for later retrieval, debugging, or analysis. It suits any project using GitHub Actions that generates artifacts such as build binaries, test reports, or logs. The action integrates directly into GitHub's native artifact storage, making it the natural choice for workflows running on GitHub.

The project receives issue reports primarily from external users rather than the core team, indicating a substantial base of adopters relying on it in production. Responses to issues and pull requests typically arrive within one to two weeks. Development activity centers on bug fixes and enhancements, with significant focus on the v4 release line.