Skip to content

AGENTS.md: use the Recoil engine file header for new files#3048

Open
tomjn wants to merge 1 commit into
beyond-all-reason:masterfrom
tomjn:docs/agents-recoil-header
Open

AGENTS.md: use the Recoil engine file header for new files#3048
tomjn wants to merge 1 commit into
beyond-all-reason:masterfrom
tomjn:docs/agents-recoil-header

Conversation

@tomjn

@tomjn tomjn commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

What

Updates the File Headers section of AGENTS.md to recommend the Recoil engine license header for new files, instead of the legacy Spring engine one:

-/* This file is part of the Spring engine (GPL v2 or later), see LICENSE.html */
+/* This file is part of the Recoil engine (GPL v2 or later), see LICENSE.html */

Also adds a note that existing Spring engine headers (Recoil is a fork of Spring) do not need a mass migration — this is guidance for new files only.

Why

A number of files in the tree already use the Recoil engine header, and it came up in review that new files should follow that convention rather than the documented Spring engine one. This aligns the doc with the intended convention.


Assisted by Claude Code.

The File Headers section recommended the legacy "Spring engine" header.
New files should use the "Recoil engine" header (already used by a number
of files in the tree). Note that existing "Spring engine" headers (Recoil
is a fork of Spring) do not need a mass migration.

Assisted by Claude Code.
@sprunk

sprunk commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

The actual rule is to follow the copyright and state who authored the code. A "new" file still has to say Spring if existing Spring code was just moved there as part of a refactor. Conversely, if an existing file is completely rewritten it can reflect that in the licence notice and say Recoil.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants