Add a programming language

Propose a new PL for the catalog. Required: language name + evidence URL. A program example is encouraged but optional — skeleton proposals are accepted (a maintainer will add the program later). Submit opens a pre-filled GitHub issue tagged pl-add; an auto-PR workflow turns the issue into a pull request that materializes languages/<Name>/meta.json, the program files, and the pl_list.txt insertion.

Existing rules in CLAUDE.md and the auto-PR workflow in docs/add_pl.md.

Language Canonical name * Aliases (optional, comma-separated) Evidence URL * — Wikipedia or official site Known file extensions (comma-separated, leading dot optional) — first one is treated as primary. E.g. .pgn or .py, .pyi, .pyx

Program example (optional — skeleton proposals accepted) Title — e.g. "Hello World", "Famous game: Adams vs Torre"

File extension — e.g. .pgn License guess (optional)

Origin URL — public URL where this code appears (GitHub, Rosetta Code, official docs) Code — paste the program (a real, non-trivial example, <200 lines)

Notes (optional)

(or open the pre-filled issue directly)

What happens after I submit?

A GitHub issue opens in this repo, tagged pl-add, carrying your form fields in a structured YAML block.
A scheduled workflow (.github/workflows/pl-add-pr.yml) picks up the issue and runs tools/process_pl_addition.py against it: validates the name isn't already in pl_list.txt, materializes languages/<Name>/meta.json and (if provided) the program files (code.<ext> + manifest.json), and appends the name to pl_list.txt.
The workflow opens a draft pull request from a feature branch pl-add/<sanitized-name>, with Resolves #<issue> in the body.
A maintainer reviews the PR (sanity-checks the evidence URL, the program source, the license). On merge, the new PL appears in the next site build.
For skeleton proposals (no program), the PR creates the meta.json but flags the missing program in the PR description; a separate follow-up commit (manual or via the agentic /loop) adds the example.