Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

TODO List

Open
#100 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

The issue is a broad checklist covering workflow, engine integration, database migration, API behavior, testing, and type definitions, but it names no files or tests. Start by separating the unchecked items into independently scoped issues and locating the relevant CLI entry points; each item is done only when its behavior and any requested tests or workflow changes are complete.

Written by the indexing model from the issue text.

Description

RT

  • 工作流里需要集成 engine 仓库的下载、install 以及 external 仓库

  • 代码里的 i18n 部分

  • 工作流里对 engine 的调用应该只需要一个命令,然后编译的相关代码放置在 engine 仓库里

  • 需要约定一个公共的测试文件夹地址放置测试过程新增的文件,然后新增一个统一的工作流去清理

  • 资源 createAsset 接口的 overwrite 参数无效异常,需要修复并补充测试例

  • db 在 mac 系统上导入内置资源会默认生成很多的 .DS_Store.meta

  • 构建进度条不匹配

  • db 支持单独的迁移流程,默认不迁移升级资源,需要支持快速的多引擎版本切换

  • refresh 的接口没有返回值,如果传入不合法的参数无法判断操作是否成功

  • db create overwrite 测试例可能出现没有覆盖成功的情况

  • cocos 命令的打开、创建功能注册

  • Engine 现在是子仓库,会有出现一个功能需要主仓库和子仓库联合 PR 才能成功,需要在 ci 里加拉取线上 pr 的工作流

  • 测试例代码如果放置在 src 下,它的定义需要单独放置,或者用工作流把编译后的代码移除

  • 内网 npm 包需要整理发到外网(开源前处理)

  • Engine 模块配置的注册、初始化、配置查询 API 还没有支持

  • 项目的打开需要做一些初始化的操作,比如在 temp 目录下生成 cc.d.ts , cc.config.schema 定义等

  • assetInfo 的 type 类型定义

  • 整体的 API 入口

    Image

  • pvr 升级的可能潜在问题排除 (https://developer.imaginationtech.com/downloads/previous-releases/)

Image

Dominant language
TypeScript
Stars
450
Forks
158
Avg merge
3d 4h
Merged PRs (30d)
33

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cocos/cocos-cli

All issues in cocos/cocos-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.