actions/checkout

Action for checking out a repo

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 7th, 2026
Created on July 19th, 2019
Open Issues & Pull Requests: 693 (+0)
GitHub issues: Enabled
Number of forks: 2,779
Total Stargazers: 8,849 (+0)
Total Subscribers: 215 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.8 days
Mean response time: 101.6 days
90th percentile: 316.2 days
Tracked items: 361

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. 62% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 281
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 956 days
Stale 30+ days: 245
Stale 90+ days: 200

Recent activity

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

Top labels

  • invalid (15)
  • enhancement (6)
  • bug (3)
  • external (1)
  • need more info (1)
  • question (1)

Detailed Description

actions/checkout is a GitHub Action that checks out a repository into the workflow's workspace so that subsequent steps can access its contents.

The action fetches a single commit by default—the ref or SHA that triggered the workflow—making it fast for typical CI/CD scenarios. It supports fetching full history across all branches and tags when needed via the `fetch-depth` parameter. The action persists the authentication token in the git configuration to enable authenticated git commands in workflow scripts, then removes it during cleanup. When Git 2.18 or higher is unavailable, it falls back to the REST API to download files.

Any workflow using GitHub Actions needs this action to access repository code. It is essential for continuous integration, testing, deployment, and any automation that requires working with repository files or running git commands. The action handles the common case efficiently while remaining flexible for workflows requiring deeper history or custom credential handling.

The project maintains security as a priority, having recently added protections against "pwn request" vulnerabilities by refusing to check out fork pull request code by default when triggered by `pull_request_target` or `workflow_run` events. The codebase was migrated to ESM to support newer versions of the Actions toolkit packages. The maintainers have stated they are not accepting contributions at this time but continue to provide security updates and fix major breaking changes. The project updates its runtime and dependencies regularly, including addressing known vulnerabilities in transitive dependencies.