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

Restructure repository branches

未关闭
#170 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
git, github-actions, shell

调研方向

Review the remaining checklist items for the main, canary, and canary-base branches, along with the Jenkins jobs and GitHub Actions workflow related to canary updates. Resolve the listed repository-layout alternatives before changing the cross-repository workflow. Done means Jenkins fetches canary, the major V8 upgrade PR is opened automatically, and canary-base is no longer needed if the patch-file approach works.

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

描述

  • Create main branch in this repository
    • Set it as default branch
  • Keep canary branch as we have today
    • Alternatively have a canary/ folder which is a copy of nodejs/node with patches applied
    • Alternatively 2 keep the V8 canary as a v8-canary branch on nodejs/node and have it as a submodule here
  • Ensure Jenkins fetches the canary branch for relevant jobs
  • Use GitHub Actions to update the canary branch
  • Use GitHub Actions to open the major V8 upgrade PR on nodejs/node
  • Drop canary-base branch on nodejs/node and use patch files on this repository instead (need to experiment to ensure it doesn't worsen our workflow)
主要语言
Shell
星标
466
派生
75
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

nodejs/node-v8 的其他 Issue

查看 nodejs/node-v8 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

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