Fix: README corrections.

.gitea/workflows/test.yml

@@ -18,6 +18,11 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
 
+      - name: Check Authentication
+        uses: ./check-token
+        with:
+          token: ${{ secrets.GH_TOKEN }}
+
       - name: Go ACME Setup
         uses: ./
         with:

.github/workflows/test.yml

@@ -18,6 +18,10 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
 
+      # Let's test the token first.
+      - name: Check Authentication
+        uses: skoszewski/setup-github-release/check-token@v1
+
       - name: Go ACME Setup
         uses: skoszewski/setup-github-release@v1
         with:

README.md

@@ -10,7 +10,7 @@ Add the action to your workflow. Authenticate with `github.token` (default) or a
 
 ```yaml
 - name: Install Tool
-  uses: koszewscy/setup-github-release@v1
+  uses: skoszewski/setup-github-release@v1
   with:
     repository: 'owner/repo'
 ```
@@ -24,7 +24,7 @@ Install the CLI tool on any destination system with Node.js 24 or newer.
 1. Clone the repository:
 
 ```bash
-git clone https://github.com/koszewscy/setup-github-release
+git clone https://github.com/skoszewski/setup-github-release
 cd setup-github-release
 ```
 
@@ -65,8 +65,8 @@ install-github-release rclone/rclone
 The action will automatically detect your OS (Linux, Windows, macOS) and architecture (x64, ARM64) and look for a matching archive. It will search for a binary named after the repository.
 
 ```yaml
-- name: Install Hugo
+- name: Install LEGO
-  uses: koszewscy/setup-github-release@v1
+  uses: skoszewski/setup-github-release@v1
   with:
     repository: 'go-acme/lego'
 ```
@@ -79,7 +79,7 @@ For projects with multiple binary versions, you can use a regex pattern (prefixe
 
 ```yaml
 - name: Install Extended Hugo
-  uses: koszewscy/setup-github-release@v1
+  uses: skoszewski/setup-github-release@v1
   with:
     repository: 'gohugoio/hugo'
     file-name: '~hugo_extended_[^a-z]' # Regex to match extended version
@@ -91,7 +91,7 @@ If the binary name is different from the repository name, like in the example of
 
 ```yaml
 - name: Install GitHub CLI
-  uses: koszewscy/setup-github-release@v1
+  uses: skoszewski/setup-github-release@v1
   with:
     repository: 'cli/cli'
     binary-name: 'gh' # Searches for 'gh' (or 'gh.exe') inside the extracted release
@@ -102,7 +102,7 @@ If the binary name is different from the repository name, like in the example of
 If you are unsure how the binary is named, use the `debug` flag to list all files in the unpacked asset, or download the asset manually to inspect its structure.
 
 ```yaml
-- uses: koszewscy/setup-github-release@v1
+- uses: skoszewski/setup-github-release@v1
   with:
     repository: 'owner/repo'
     debug: true
@@ -150,7 +150,9 @@ Options:
 
 ## GitHub Token Verification
 
-The project includes a utility to verify the validity of your GitHub token:
+The project includes a utility to verify the validity of your GitHub token.
+
+### CLI Utility
 
 ```bash
 check-github-token <token>
@@ -158,6 +160,20 @@ check-github-token <token>
 
 If no token is provided as an argument, it will attempt to read from the `GITHUB_TOKEN` environment variable.
 
+### GitHub Action
+
+You can also use the `check-token` subaction in your workflows:
+
+```yaml
+- name: Verify Token
+  uses: skoszewski/setup-github-release/check-token@v1
+  with:
+    repository: 'actions/checkout' # Optional, defaults to actions/checkout
+    token: ${{ secrets.MY_TOKEN }}
+```
+
+If the `token` input is not provided, it will read from the `GITHUB_TOKEN` environment variable.
+
 ## Asset Selection Procedure
 
 The list of assets from the latest release is filtered based on the following rules:
@@ -187,7 +203,7 @@ The list of assets from the latest release is filtered based on the following ru
 8. `{{SYSTEM}}` is replaced with the detected operating system regex:
 
     - For Linux: `linux`.
-    - For MacOS: `(darwin|macos|mac|osx)`.
+    - For MacOS: `(darwin|macos|mac)`.
     - For Windows: `(windows|win)`.
 
 9. `{{ARCH}}` is replaced with the detected architecture regex:

check-token/action.yml

@@ -0,0 +1,15 @@
+name: 'check-token'
+description: 'Verify the validity of a GitHub token'
+author: 'Slawomir Koszewski with GitHub Copilot assistance'
+inputs:
+  repository:
+    description: 'The GitHub repository to check (e.g., owner/repo)'
+    required: false
+    default: 'actions/checkout'
+  token:
+    description: 'The GitHub token to verify'
+    required: false
+    default: ${{ github.token }}
+runs:
+  using: 'node24'
+  main: '../dist/check-token-action.js'

package.json

@@ -11,7 +11,8 @@
     "build:action": "esbuild src/index.ts --bundle --platform=node --target=node24 --outfile=dist/index.js --minify",
     "build:cli": "esbuild src/cli.ts --bundle --platform=node --target=node24 --outfile=dist/cli.js --minify --banner:js=\"#!/usr/bin/env node\"",
     "build:check-token": "esbuild src/check-token.ts --bundle --platform=node --target=node24 --outfile=dist/check-token.js --minify --banner:js=\"#!/usr/bin/env node\"",
-    "build": "npm run build:action && npm run build:cli && npm run build:check-token",
+    "build:check-token-action": "esbuild src/check-token-action.ts --bundle --platform=node --target=node24 --outfile=dist/check-token-action.js --minify",
+    "build": "npm run build:action && npm run build:cli && npm run build:check-token && npm run build:check-token-action",
     "format": "prettier --write '**/*.ts'",
     "format-check": "prettier --check '**/*.ts'",
     "lint": "eslint src/**/*.ts",

src/check-token-action.ts

@@ -0,0 +1,24 @@
+import * as core from '@actions/core';
+import { fetchLatestRelease } from './core/downloader';
+
+async function run() {
+  try {
+    const repository = core.getInput('repository') || 'actions/checkout';
+    const token = core.getInput('token') || process.env.GITHUB_TOKEN;
+
+    if (!token) {
+      core.setFailed('No GitHub token provided as an input or found in GITHUB_TOKEN environment variable.');
+      return;
+    }
+
+    core.info(`Verifying GitHub token using repository ${repository}...`);
+    // Attempt to list latest release of the specified repository as a test
+    await fetchLatestRelease(repository, token);
+
+    core.info('Success: The provided GitHub token is valid and has sufficient permissions to access the repository.');
+  } catch (error: any) {
+    core.setFailed(`GitHub token verification failed. Reason: ${error.message}`);
+  }
+}
+
+run();