armbian-build/.github/workflows
dependabot[bot] c7c9ad8755 build(deps): bump tj-actions/changed-files from 47.0.1 to 47.0.2
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 47.0.1 to 47.0.2.
- [Release notes](https://github.com/tj-actions/changed-files/releases)
- [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md)
- [Commits](e002140703...8cba46e29c)

---
updated-dependencies:
- dependency-name: tj-actions/changed-files
  dependency-version: 47.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-02-10 00:06:03 +01:00
..
data-jira-ticket.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
data-sync-board-list.yml Automation: when board data changes on push, execute inventory rebuild at armbian.github.io 2026-02-04 22:18:50 +01:00
data-sync-labels.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
data-sync-maintainers.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
data-sync-tools.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
infrastructure-dispatch-to-fork.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
infrastructure-mirror-to-codeberg.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-announce-merge.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-announce-pr.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-auto-label.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-build-artifacts.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-check-board-assets.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-check-kernel-security.yml build(deps): bump tj-actions/changed-files from 47.0.1 to 47.0.2 2026-02-10 00:06:03 +01:00
maintenance-clean-workflow-logs.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-label-on-approval.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-lint-scripts.yml build(deps): bump tj-actions/changed-files from 47.0.1 to 47.0.2 2026-02-10 00:06:03 +01:00
maintenance-listen-review.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-rewrite-kernel-configs.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-rewrite-kernel-patches.yml add env for step 2026-02-09 11:50:24 +01:00
maintenance-security-scan.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-watchdog.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-welcome-issue.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
maintenance-welcome-pr.yml ci: organize GitHub Actions into meaningful categories 2026-01-16 15:55:01 +01:00
README.md GH Actions: Update README.md on how to create and use ARMBIAN_SELF_DISPATCH_TOKEN 2024-03-09 20:03:52 +01:00

Runners requirements

  • big (6-16 cores, 64Gb SSD, 16Gb memory, 2Gb swap)
  • small (4 cores, 64Gb SSD, 8Gb memory, 2Gb swap)

Preparation

Adding x86 runner to your Jammy VM (check here if any changes):

$ mkdir actions-runner 
$ cd actions-runner
$ curl -o actions-runner-linux-x64-2.294.0.tar.gz -L https://github.com/actions/runner/releases/download/v2.294.0/actions-runner-linux-x64-2.294.0.tar.gz
$ tar xzf ./actions-runner-linux-x64-2.294.0.tar.gz

Configuration

Once asked, tag your runner accordingly:

  • small
  • big
  • arm64

Start the configuration experience

$ ./config.sh --url https://github.com/armbian --token XXXXXXXXXXXXXXXXXXXXXXXXXXX

You need to get a valid token from our DevOps team to proceed.

Create startup scripts

sudo ./svc.sh install # install
sudo ./svc.sh start   # start
sudo ./svc.sh status  # check

Use workflows in forked repositories

forked-helper.yml workflow helper can help to run custom workflows on the forked repositories.

  1. Create a fine-grained Personal Access Token (PAT) with the repo scope and store it as a secret. It needs the following permissions on the target repositories:
    • contents: read & write
    • metadata: read only (automatically selected when selecting the contents permission)
  2. Create a secret named ARMBIAN_SELF_DISPATCH_TOKEN on your repository with security_events permissions. To do this, head to your forked repository, go to Settings on the top bar, select Secrets and variables and then Actions. From here you can create a new repository secret.
    • Name: ARMBIAN_SELF_DISPATCH_TOKEN
    • Secret: Paste your fine-grained Personal Access Token that you created in step 1 here
  3. Helper will dispatch repository_dispatch event armbian on push, release, deployment, pull_request and workflow_dispatch events. All needed event details you can find in client_payload property of the event.
  4. Create empty default branch in forked repository
  5. Create workflow with repository_dispatch in default branch.
  6. Run any need actions in this workflow.

Workflow example:

name: Test Armbian dispatch

on:
  repository_dispatch:
    types: ["armbian"]

jobs:
  show-dispatch:
    name: Show dispatch event details
    runs-on: ubuntu-latest
    steps:
      - uses: hmarr/debug-action@v2