Socket-free jobs move from runs-on: docker to runs-on: light, which both runners carry (host1, and host2 over the wg-hosts tunnel), so they run on whichever host is free. Jobs that mount the docker socket stay on docker (host1 only).
Socket-free jobs move from runs-on: docker to runs-on: light, which both runners carry (host1, and host2 over the wg-hosts tunnel), so they run on whichever host is free. Jobs that mount the docker socket stay on docker (host1 only).
Both runners carry `light` (host1, and host2 over the wg-hosts link), so
these jobs run on whichever host is free. Jobs that mount the docker socket
keep `runs-on: docker`, which only host1 has.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Socket-free jobs move from runs-on: docker to runs-on: light, which both runners carry (host1, and host2 over the wg-hosts tunnel), so they run on whichever host is free. Jobs that mount the docker socket stay on docker (host1 only).