nf publish does not read .gitignore or .nfignore
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 57/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- node.js, typescript
- 领域
- build-system, cli
调研方向
Start at the nf publish packaging flow in @nanoforge-dev/cli, then inspect how the editor reads .nfignore for its file tree and how --dry-run displays packed files. The issue says to apply .nfignore and .gitignore from the package folder before the built-in deny list; done means matching files are absent from both the packed file list and dry-run output. The registry library move is described as not merged yet, so check that branch context first.
由索引模型根据 Issue 内容生成。
描述
Which package is this feature request for?
@nanoforge-dev/cli
Which command is this feature request for?
publish
Feature
nf publish packs only what the manifest names, but it doesn't read .gitignore or a .nfignore. A file inside a named folder (src/, assets/) that the project ignores, such as a generated or local file, is still published unless its name is on the built-in deny list.
Ideal solution or implementation
Read .nfignore (the editor already has one, .nfignore, for its file tree) and .gitignore of the package folder, and leave out what they match, before the deny list. The packed file list and --dry-run show the result.
Alternative solutions or implementations
Only .nfignore, so that publishing doesn't depend on git's rules.
Other context
Found during the feat/registry-lib change (not merged yet): @nanoforge-dev/registry moves from the editor to libs/registry, and nf install/publish/unpublish use it.
- 主要语言
- TypeScript
- 星标
- 2
- 派生
- 2
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 17
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NanoForge-dev/CLI 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 88/100
NanoForge-dev/CLI#294 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
NanoForge-dev/CLI#293 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
NanoForge-dev/CLI#292 ·
维护者通常 1 天内回复
-
command:dev enhancement good first issue refactor
难度 2/5 1-3 小时 新手友好度 78/100
NanoForge-dev/CLI#281 ·
维护者通常 1 天内回复
-
bug command:build good first issue
难度 2/5 1-3 小时 新手友好度 88/100
NanoForge-dev/CLI#276 ·
维护者通常 1 天内回复
查看 NanoForge-dev/CLI 的全部 Issue
相似的 Issue
-
Mend: dependency security vulnerability
难度 1/5 1-3 小时 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
难度 2/5 1-3 小时 新手友好度 65/100
growilabs/growi#12246 · 3 条评论 ·
维护者通常 1 天内回复
-
🐛 The Rulekeeper - An index run that gives up on the lock ends Succeeded可能已有人在做 @github-actions 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
SSWConsulting/SSW.Rules#2809 · 1 条评论 ·
维护者通常 1 天内回复