actions-able: A GitHub Organisation for GitHub Actions Tooling

Over the past few years I have built and maintained several GitHub Actions under my personal account — github-slug-action , drawio-export-action , and others. Those actions remain under my personal namespace to avoid breaking existing user workflows — changing the repository path would force every consumer to update their workflow files. They are, however, still actively maintained and listed in the organisation’s readme.

With that in mind, actions-able was created as a GitHub organisation for new GitHub Actions tooling and community resources that can live under a shared, organisation-level namespace from the start.

The name is a small play on words — actions that are able, ready to use. The organisation is maintained together with @fhgbaguidi and is open to contributions from anyone.

envsubst-action

The first action published under the organisation is envsubst-action . It wraps the envsubst utility from GNU gettext so you can substitute environment variables inside files directly in your workflow, without installing extra dependencies on the runner.

A typical use case is templating configuration files before deployment. Imagine a config.template.json that contains placeholders like ${API_URL} and ${APP_VERSION}. A single step turns it into a ready-to-deploy configuration:

- uses: actions-able/envsubst-action@v1
  env:
    API_URL: https://api.example.com
    APP_VERSION: ${{ github.sha }}
  with:
    input: config.template.json
    output: config.json

The action supports processing multiple files at once using glob patterns, and it lets you configure a working directory and output suffix when you need more control. It runs on Alpine Linux, keeping the image lightweight and fast to pull.

The current release is v1.2.0. You can find full documentation and examples in the repository readme .

awesome-actions

The second project is awesome-actions , a maintained fork of the well-known sdras/awesome-actions list. The original repository was a go-to resource for discovering GitHub Actions across every category imaginable — from CI/CD and testing to deployment and security scanning. Over time, maintenance slowed down and many entries became outdated or pointed to archived repositories.

The fork under actions-able picks up where the original left off. It keeps the same comprehensive structure — official actions, community actions organised by language and purpose, deployment targets, and more — while actively reviewing and updating entries. Archived and deleted repositories are tracked transparently so you know exactly what is still alive.

If you maintain a GitHub Action and want it listed, or if you spot a broken link, pull requests are welcome. The list is licensed under CC0, so you can use and share it freely.

Outside-organisation repositories

Not every action maintained by the team lives under the actions-able namespace. Some repositories — like github-slug-action and drawio-export-action — stay under their original owner’s account. Moving them would change the action path and break every workflow that references them. Rather than force that migration on users, these actions are maintained as part of the actions-able effort while keeping their existing namespace intact. They are listed in the organisation readme so you can discover them alongside the rest of the collection.

Getting involved

The organisation participates in Hacktoberfest each year, so October is a particularly good time to send your first contribution. But contributions are welcome year-round — whether that is a bug report, a documentation improvement, or a brand-new action idea.

You can find everything at github.com/actions-able .