Skip to content

Docs: No new top-level folders without approval #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
b-re-w merged 1 commit into from
Oct 3, 2026
Merged

Docs: No new top-level folders without approval #116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@ ask first.**

Writing to *another* repository is not an exception either. Do it only when told to work there.

### Do not add top-level folders

**Never add a new directory (or a new file) at the repository root on your own.** The root layout is
the maintainer's: source modules, `docs/`, `gradle/`, `.github/` and the files that tools require
there. Work belongs inside an existing module or directory — sources under `src/<sourceSet>/`,
CI-only scripts under `.github/scripts/`, temporary files under the git-ignored `.tmp/`. If you think
a new top-level entry is needed, propose it (what, why, which alternatives inside existing
directories you ruled out) and wait for approval. This was added after unapproved root folders
(`ksp-fixtures/`, `tools/`, `kotlin-js-store/`, `iosApp/`, `sample/python`) had to be dismantled.

## 3. Worktrees link large artefacts instead of copying them

A worktree is a full checkout. Copying large untracked artefacts (prebuilt runtimes, vendored trees,
Expand Down
Loading