Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[workshop-sync] side-quest-24-01-runner-infrastructure.md: ephemeral/JIT runner and proxy-env-var guidance unsupported by self-hosted-runners re

已关闭 适合新手
  • 哪里不对？
#4,449 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
documentation

调研方向

从 workshop/side-quest-24-01-runner-infrastructure.md 开始，将其中关于 runner 和网络的指导与链接的 self-hosted-runners 参考资料进行比较。更新 ephemeral/JIT 和代理部分，使其符合文档中说明的 runner 配置和网络隔离，并使 MCP 服务器说明与 network.allowed 保持一致。不准确的说法得到纠正，且 issue 中列出的准确示例保持不变后，即为完成。

由索引模型根据 Issue 内容生成。

描述

documentation

Workshop file reviewed

workshop/side-quest-24-01-runner-infrastructure.md

Problem

  1. The "Ephemeral and JIT runners" section states:

Ephemeral runners are destroyed after a single job ... Register one using the ephemeral flag ... Just-in-time (JIT) runners are provisioned on demand and deregistered immediately after use. They require a registration token scoped to your organisation or repository and are typically managed by a runner controller such as actions-runner-controller.

This section links to https://github.github.com/gh-aw/reference/self-hosted-runners/, but that page contains no mention of ephemeral runners, JIT runners, registration tokens, or actions-runner-controller registration flags.

  1. The "Proxy and network requirements" section instructs learners to set host-level proxy environment variables:
HTTPS_PROXY=(proxy.example.com/redacted)
HTTP_PROXY=(proxy.example.com/redacted)
NO_PROXY=localhost,127.0.0.1,github.example.com

This is not documented anywhere in the gh-aw reference docs as the mechanism for self-hosted runner network configuration.

  1. The "Network isolation" section frames "MCP tool servers" as independently-reachable endpoints, separate from network.allowed.

Current correct behaviour

The actual reference/self-hosted-runners/ page documents:

  • The runs-on frontmatter field (string/array/object forms) to target self-hosted runners.
  • require_self_hosted_runners in .github/workflows/aw.json (or --require-self-hosted-runners CLI flag) to enforce self-hosted runners on all generated jobs.
  • ARC Docker-in-Docker topology via runner.topology: arc-dind, including GH_AW_DOCKER_SOCK_PATH/GH_AW_DOCKER_SOCK_GID env var overrides for split-daemon setups.
  • Network isolation is enforced via AWF's own internal Docker network topology (an internal awf-net bridge with no internet route) and a dual-homed Squid proxy inside the Docker daemon's domain — not via host-level HTTPS_PROXY/HTTP_PROXY/NO_PROXY env vars on the runner machine.
  • Documented outbound network requirements: api.githubcopilot.com (or enterprise Copilot endpoint), github.com (or GHES instance), ghcr.io (to pull the MCP gateway image), and any domains in network.allowed.

Suggested fix

  • Remove or rewrite the "Ephemeral and JIT runners" section to cover gh-aw-documented self-hosted runner configuration instead: runs-on, require_self_hosted_runners, and runner.topology: arc-dind for ARC DinD setups.
  • Replace the HTTPS_PROXY/HTTP_PROXY/NO_PROXY guidance with an explanation of AWF's internal Squid-proxy network isolation and the documented outbound endpoint list (Copilot/model endpoint, GitHub/GHES, ghcr.io, plus network.allowed domains).
  • Reframe "MCP tool servers" access as governed by the network.allowed frontmatter field rather than a separately reachable endpoint category.
  • The network.allowed example and firewall.md artifact mention in this file are accurate and do not need changes.

Reference: https://github.github.com/gh-aw/reference/self-hosted-runners/ (confirmed reachable, HTTP 200; verified no "ephemeral"/"JIT"/proxy-env-var content present)

Generated by 🔍 Workshop Sync Check · copilot · auto · 239.5 AIC · ⌖ 8.28 AIC · ⊞ 9.2K · ◷

  • expires on Oct 12, 2026, 5:49 AM UTC
主要语言
JavaScript
星标
56
派生
40
平均合并
2 天 15 小时
30 天内合并 PR
14

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/gh-aw-workshop 的其他 Issue

查看 githubnext/gh-aw-workshop 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。