Workspace layout: ignored directories (dist/, build/, node_modules/, scratch/)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- git
- Domain
- build-system, documentation
Research direction
Start with the repository’s .gitignore and existing workspace documentation, then review the requested source, output, and scratch zones. Add the ignore rules and scratch/README.md described in the issue, and verify that deleting scratch/ does not break the repository, build, or documentation.
Written by the indexing model from the issue text.
Description
Question
Establish the three-zone workspace layout:
| Zone | Directory | Committed | Rebuilt | Lifetime |
|---|---|---|---|---|
| Source | src/, docs/, tests/, assets/ |
Yes | Never | Permanent |
| Output | dist/, build/, target/, node_modules/ |
No | Always | Until next build |
| Scratch | scratch/ |
No | Never | Disposable |
Key rules:
- Output is ignored because it is derived. Committing build artifacts creates a second source of truth.
- Scratch is ignored because it is private. Give it a
README.mdthat survives the ignore rule. - The defining test: deleting
scratch/entirely must never break the repository, the build, or the documentation.
Decision needed: Configure .gitignore for these zones. Create scratch/README.md explaining the convention. Ensure dist/, build/, node_modules/ are ignored.
Label: wayfinder:task
Part of #2517
Blocks: #2518
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 41m
- Merged PRs (30d)
- 345
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MoonshotAI/kimi-code
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
MoonshotAI/kimi-code#3947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-code#3836 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MoonshotAI/kimi-code#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-code#3755 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-code#3627 ·
All issues in MoonshotAI/kimi-code
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100