Import the gh-aw cracktro skill and interactive deck

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github, typescript

调研方向

The issue pins upstream content to commit ea67aef627d4fbfbbfd5a956cb2d74f0574ce645 and notes 51 cracktro path files before integration work. First review the repository’s file count and approval requirements, then verify the upstream notices and asset rights. Done means the approved scope is integrated, checks pass, and the required waiver and brand approvals are documented before merge.

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

描述

Scope

Import the complete cracktro skill, standalone interactive deck, assets, slide metadata, tests, and related documentation from github/gh-aw at commit ea67aef627d4fbfbbfd5a956cb2d74f0574ce645, adapting integration to Squad while preserving functionality and upstream provenance.

Acceptance criteria

  • Include the upstream deck assets, including images and font, subject to the required repository waiver and applicable brand approvals.
  • Preserve applicable MIT and SIL OFL notices; verify mascot and other asset usage rights.
  • Integrate slide metadata and documentation, and validate the deck and existing repository checks.
  • Request the binary-file waiver in the PR and obtain approval from the appropriate Lead/Quality owner in a PR review comment before merge.

Coordination

The pinned upstream tree contains 51 files under cracktro paths alone, before related docs/tests or integration changes. Repository instructions require stopping for changes over 20 files, and PR requirements call changes over 50 files a red flag requiring split or explicit written approval. Confirm the permitted scope and approvals before implementation. GitHub brand guidance requires Brand & Marketing Design approval for public mascot usage; verify that any existing approval covers this publication.

主要语言
TypeScript
星标
3.4k
派生
516
平均合并
1 天 15 小时
30 天内合并 PR
116

环境准备

从这里开始

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

github/squad 的其他 Issue

查看 github/squad 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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