sdras/awesome-actions

Awesome Actions is a curated list of GitHub Actions, maintained by Sarah Drasner. GitHub Actions is GitHub's built-in automation system: small reusable scripts that run in response to events in a repository (a push, a pull request, an issue comment, a tag, a schedule) on Linux, Windows, or macOS virtual machines, or inside a container. This repo does not add new automation, it points to existing actions that other people have built. The README opens with a short description of what GitHub Actions is, then a table of contents, and then long sections of links. The Official Resources part covers things like the official documentation, the GitHub organisation that hosts Actions infrastructure, starter workflows, and the official runner. It also lists the official setup actions for popular languages (Node, Python, Go.NET, Ruby, Java, Elixir, Julia, Haskell) and the building blocks for writing your own action in JavaScript, TypeScript, or as a Docker container. The much longer Community Resources part is where third-party actions are gathered, sorted into categories: tools to manage GitHub itself (labels, releases, project cards, wiki pages), utilities, static and dynamic code analysis, monitoring, pull-request helpers, deployment to various clouds, frontend tooling, machine-learning ops, build helpers, databases, networking, localization, and even a Fun bucket. Each entry is one bullet with a short description and a link to the action's own repository. The list also mentions tools that run GitHub Actions outside GitHub itself, such as nektos/act, which lets you run a workflow locally in a terminal, and wflow, which gives a small web interface for the same idea. Practical extras include actions for cutting a release, uploading and downloading build artifacts, caching dependencies between runs, and pushing a built Docker image to Docker Hub. The repo is meant as a shopping list. If you want a workflow to do something specific, you scan the relevant section, click through to the action's page, and read its own README to learn the inputs and outputs. The list itself has no installation steps, it is a static document of links kept current by community pull requests.