npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@adguard/github-actions-runner

v1.1.1

Published

A GitHub Action runner tool to automate repository mirroring, streamline command execution, and manage artifacts with enhanced logging.

Downloads

312

Readme

@adguard/github-actions-runner

Description

@adguard/github-actions-runner is a versatile command-line interface (CLI) tool designed to facilitate automation with GitHub Actions. It simplifies tasks such as repository mirroring, command execution, and artifact management. By integrating with GitHub's robust API, it provides a seamless approach to running and managing workflows, ideal for developers and DevOps engineers looking to enhance their CI/CD processes.

This tool is designed to offer greater flexibility when interacting with GitHub Actions, allowing you to automate workflows, manage artifacts, and pass secrets securely. Whether you're a DevOps engineer or a software developer, @adguard/github-actions-runner enables you to focus on coding and development, reducing the overhead of managing pipelines.

Installation

To get started with using @adguard/github-actions-runner, ensure that Node.js is installed on your system, then install the package with one of the following methods:

  • Using pnpm:
pnpm install @adguard/github-actions-runner
  • Using npm:
npm install @adguard/github-actions-runner
  • Using yarn:
yarn add @adguard/github-actions-runner

Usage

The CLI tool can trigger and manage GitHub Actions with the following command format:

Usage: github-actions-runner run-action [options]

Triggers a GitHub Action workflow run

Options:
  -r, --repo <repo>                                repository specified as "owner/repo", e.g., "AdguardTeam/GithubActionsRunner"
  -w, --workflow <workflow>                        workflow file to trigger, e.g., "test.yml"
  -b, --branch <branch>                            branch name
  -c, --rev <revision>                             commit revision
  -a, --artifacts-path [artifacts-path]            local path for downloading artifacts; if not specified, artifacts will not be downloaded
  --commit-timeout [timeout-sec]                   timeout in seconds to wait for the commit to appear in the repository (default: 300 seconds)
  --branch-timeout [timeout-sec]                   timeout in seconds to wait for the branch to appear in the repository (default: 300 seconds)
  --workflow-run-creation-timeout [timeout-sec]    timeout in seconds to wait for the workflow run to be created (default: 300 seconds)
  --workflow-run-completion-timeout [timeout-sec]  timeout in seconds to wait for the workflow run to be completed (default: 300 seconds)
  -s, --secret <KEY=VALUE>                         Secret key-value pair for the GitHub Action workflow, e.g., "API_KEY=12345".You can add multiple secrets by repeating the option. (default: [])
  --sync-secrets                                   Sync secrets with the repository secrets. Secrets which were not provided will be removed (default: false)
  -v, --verbose                                    enable verbose mode (default: false)
  -h, --help                                       display help for command

Note:

Ensure that you have a valid GITHUB_TOKEN set in your environment variables for authentication.

Example:

To run a GitHub Action workflow with the specified configuration:

github-actions-runner run-action \
  --repo "AdguardTeam/GithubActionsRunner" \
  --workflow "build.yml" \
  --branch "master" \
  --rev "abc1234" \
  --artifacts-path "./downloads" \
  --commit-timeout 300 \
  --branch-timeout 300 \
  --workflow-run-completion-timeout 300 \
  --secret "API_KEY=12345" \
  --secret "API_KEY2=67890" \
  --verbose

Docker

This CLI tool is available as a Docker image, enabling its use in containerized environments. There are two Docker images available, each serving different use cases.

Standard Docker Image

The standard Docker image includes an ENTRYPOINT to simplify command execution. You can pull it from the GitHub Container Registry and run it like this:

docker pull ghcr.io/adguard/github-actions-runner:latest

To run the image, use the following command:

docker run --rm -it ghcr.io/adguard/github-actions-runner:latest run-action \
  --repo "AdguardTeam/GithubActionsRunner" \
  --workflow "build.yml" \
  --branch "master" \
  --rev "abc1234" \
  --artifacts-path "./downloads" \
  --commit-timeout 300 \
  --branch-timeout 300 \
  --verbose

Docker Image without ENTRYPOINT

This alternative Docker image doesn't set an ENTRYPOINT, providing more flexibility for advanced use cases. Pull it from the GitHub Container Registry and run it like this:

docker pull ghcr.io/adguard/github-actions-runner:latest-ci

To run the image, you need to specify the command manually:

docker run --rm -it ghcr.io/adguard/github-actions-runner:latest-ci /bin/sh

In this mode, you can execute commands manually inside the container or create custom entry points for specific workflows.

Contributing

Contributions to extend the functionality or improve the tool are welcome. Please refer to the project's repository on GitHub to submit issues or pull requests.