actions/starter-workflows

Accelerating new GitHub Actions workflows

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 5th, 2026
Created on July 29th, 2019
Open Issues & Pull Requests: 507 (+0)
GitHub issues: Enabled
Number of forks: 7,306
Total Stargazers: 12,021 (+0)
Total Subscribers: 596 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.7 hours
Mean response time: 16.5 days
90th percentile: 58.3 days
Tracked items: 145

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 283
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 349 days
Stale 30+ days: 267
Stale 90+ days: 236

Recent activity

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

Top labels

  • no-issue-activity (4)
  • *off-topic (1)

Detailed Description

Starter Workflows is a collection of template workflow files that help developers get started with GitHub Actions.

The project solves the problem of workflow creation friction by providing pre-built YAML templates for common automation scenarios. When a developer creates a new GitHub Actions workflow through the Actions tab in a repository, these starter templates are presented as options, allowing them to begin with working examples rather than starting from scratch. The templates are organized by use case: continuous integration, deployments, automation, code scanning, and GitHub Pages. Each template consists of a workflow YAML file paired with a properties JSON file containing metadata like display name, description, icon, creator attribution, and category tags that control how the template appears in the GitHub UI.

Developers should use these templates when setting up their first GitHub Actions workflows or when implementing common patterns they haven't automated before. The templates cover a range of programming languages and technology stacks, with categorization that surfaces relevant templates based on the detected language and tech stack of the repository. This makes the tool most valuable for teams new to GitHub Actions or those seeking established patterns for standard CI/CD tasks.

The project is not accepting external contributions at this time, with the maintainers directing their resources to other areas of GitHub Actions. The team continues to provide security updates and will address major breaking changes. Bug reports remain welcome through the repository's issue tracker, while support requests and questions are directed to the Community Discussions area.