ludic/.forgejo/pull_request_template.md at b205dd8dfd2c79cff5678c5b6ddf732ff087aed2

Orkuncakilkaya 7d64a617d4 docs: add CONTRIBUTING, code of conduct, and Forgejo templates

Contributor onboarding for the self-hosted toolchain (issue #37):

- `CONTRIBUTING.md`: prerequisites, the bootstrap one-liner, the dev loop
  (`bin/x reseed` -> `bin/x bootstrap-cfree` -> `bin/x test`), stdlib-addition
  guidance, and the code/commit conventions (Conventional Commits, ludic-fmt,
  one-job-per-file, Ludic-not-C/Python/JS for new tooling).
- `.forgejo/issue_template/`: bug, proposal, and cleanup/DX templates.
- `.forgejo/pull_request_template.md`: a checklist covering tests, the
  bootstrap fixpoint, formatting, docs/inventory, and commit style.
- `.forgejo/CODEOWNERS` and a short `CODE_OF_CONDUCT.md`.

Closes #37

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-08-30 16:46:30 +03:00

925 B

Raw Blame History

What & why

Closes #

Checklist

bin/x test passes.
For compiler/runtime changes: bin/x reseed && bin/x bootstrap-cfree still reaches the self-hosting fixpoint with no C compiler in the loop.
ludic-fmt leaves the touched files unchanged (2-space, LF, UTF-8).
New/changed stdlib symbols are documented under docs/language/** and registered in tools/docgen/inventory.json (python3 tools/docgen/check.py passes).
Commits follow Conventional Commits.
No new C / Python / JS in tooling (Ludic only), and no generated artifacts committed outside build/ / bin/.

925 B Raw Blame History

What & why

Checklist

Notes for reviewers

925 B

Raw Blame History