Skip to content

Github Workflow

David Liu edited this page Sep 19, 2024 · 4 revisions

Badge

  • Repository tab Actions -> Select a workflow (listed at left) -> [Create status badge] button (upper-right of workflow details) -> Event: default

Actions

action.yaml

Runner

Github Cloud hosts runner

  • Self-lift source
  • hardware
    • Hardware specification for Windows and Linux virtual machines: Standard_DS2_v2 in Microsoft Azure
      • 2-core CPU
      • 7 GB of RAM memory
      • 14 GB of SSD disk space
    • GitHub hosts macOS runners in GitHub's own macOS Cloud. Hardware specification for macOS virtual machines
      • 3-core CPU
      • 14 GB of RAM memory
      • 14 GB of SSD disk space
    • The GitHub-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work.
    • To get a list of IP address ranges that GitHub Actions uses for GitHub-hosted runners, you can use the GitHub REST API. The list of GitHub Actions IP addresses returned by the API is updated once a week.
  • GitHub runners are placed in Azure. Ping doesn't work in azure by design.
  • Windows Runner does not support nested virtualization, which is required to run Linux containers directly
  1. Settings -> Actions -> Add runner
Clone this wiki locally