Skip to content

docs: remove duplicate lean_proof_env README entry and renumber index#445

Open
amethystani wants to merge 2 commits intoNousResearch:mainfrom
amethystani:fix/remove-duplicate-lean-env-entry
Open

docs: remove duplicate lean_proof_env README entry and renumber index#445
amethystani wants to merge 2 commits intoNousResearch:mainfrom
amethystani:fix/remove-duplicate-lean-env-entry

Conversation

@amethystani
Copy link
Copy Markdown

Summary

The community README.md has two separate entries both pointing to environments/community/lean_proof_env/:

  • Entry 1 — brief entry by GabinFay from the original hackathon contribution
  • Entry 15 — detailed entry by justin5764 added as a separate PR

Since only one lean_proof_env/ directory exists, having two entries is confusing and misleading.

What changed

  • Entry 1 updated to credit both contributors (GabinFay + justin5764) with a comprehensive feature description
  • Entry 15 (the duplicate) removed
  • Entries 16–29 renumbered to 15–28 to keep the index sequential

No code changes

Documentation only — no environment code, configs, or tests were modified.

Test plan

  • Verified lean_proof_env/ only has one directory in the repo
  • Verified no open PR already addresses this
  • Entry 1 now contains all relevant details from both original entries
  • Index is sequential 1–28 after renumbering (no gaps)

amethystani and others added 2 commits April 12, 2026 13:51
The community README had two entries pointing to the same
lean_proof_env/ directory:
- Entry 1 (GabinFay) — brief, from original hackathon submission
- Entry 15 (justin5764) — detailed, added later as a separate PR

This consolidates both into entry 1, crediting both authors and
keeping the more comprehensive feature description. The duplicate
entry 15 is removed and entries 16–29 are renumbered to 15–28
to keep the index sequential.
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.

1 participant