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

chore: upstream dfinity/icp-cli moved to v1.7.0

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with .agents/upstream-tracking.md and compare the v1.6.0 and v1.7.0 CLI references. Review every icp command and flag in docs/, paying particular attention to the new icp canister uninstall and icp cycles buy sections and the link slug procedure. Update affected pages and set the pin to v1.7.0 in .sources/upstream.json; done when the docs reflect the release or the PR explains that only the pin changed.

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

描述

upstream-dfinity-icp-cli upstream-sync

dfinity/icp-cli has moved past the ref the docs are verified against.

Pinned in .sources/upstream.json v1.6.0
Latest release v1.7.0
Compare https://github.com/dfinity/icp-cli/compare/v1.6.0...v1.7.0
Published reference https://cli.internetcomputer.org/

What to re-check

Every icp command and flag in docs/. A new minor also moves the cli.internetcomputer.org link slug (AGENTS.md 'Linking rules'), so check the slug procedure in .agents/upstream-tracking.md when the minor changes.

docs/reference/cli.md

40 line(s) added, 0 removed.

New sections:

  • icp canister uninstall
  • icp cycles buy

Full diff:

diff <(curl -sL https://raw.githubusercontent.com/dfinity/icp-cli/v1.6.0/docs/reference/cli.md) \
     <(curl -sL https://raw.githubusercontent.com/dfinity/icp-cli/v1.7.0/docs/reference/cli.md)

How to close this

  1. Review the changes above against the pages named under "What to re-check".
  2. Update those pages if anything they state has changed.
  3. Set pinned to v1.7.0 in .sources/upstream.json in the same PR.

If nothing in the docs is affected, bump the pin on its own and say so in the PR.

Procedure: .agents/upstream-tracking.md

主要语言
JavaScript
星标
4
派生
4
平均合并
18 小时 14 分钟
30 天内合并 PR
10

环境准备

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

从这里开始

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

dfinity/developer-docs 的其他 Issue

查看 dfinity/developer-docs 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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