chore: point PyPI homepage + README + llms.txt at eplang.me#95
Conversation
- pyproject [project.urls] Homepage -> https://eplang.me (shows on the PyPI sidebar from the next release); add eplang/epl/english-programming-language discovery keywords - README header: Official Website link first - llms.txt: bump to v10.2.0, add official-site link (mirrored to the website repo, now served at https://eplang.me/llms.txt)
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
epl | 1b0fc89 | Commit Preview URL Branch Preview URL |
Jul 20 2026, 12:41 PM |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
WalkthroughProject documentation and package metadata now reference ChangesProject metadata and contact updates
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@llms.txt`:
- Around line 3-7: Synchronize the version claims between the llms.txt
introduction and the built-ins verification statement in llms-full.txt: update
the v10.1.1 reference near the built-ins documentation to match EPL v10.2.0, or
explicitly clarify that it refers to an older verification scope. Ensure users
are not presented with conflicting version guidance.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: cd144fcf-8349-4226-b57c-970212ec1810
📒 Files selected for processing (3)
README.mdllms.txtpyproject.toml
| > EPL is a programming language with English syntax (v10.2.0). Write code in plain English — apps, web servers, APIs, desktop GUIs, and mobile apps. Install: `pip install eplang`. Run: `epl run file.epl`. By default `epl run` executes on a bytecode VM (real closures + full control-flow parity with the reference interpreter); `--interpret` selects the tree-walking interpreter. EPL also transpiles to Python/JS/Node/Kotlin/MicroPython, compiles native binaries (`epl build`, with type inference for untyped functions), and exports native mobile/desktop projects (`epl android`/`ios`/`desktop`, with `--webview` to ship the real web app unchanged). | ||
|
|
||
| ## Documentation | ||
|
|
||
| - [Official Website](https://eplang.me/): Homepage with live playground and install guide |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Synchronize the documentation version claims.
llms.txt now advertises EPL v10.2.0, while llms-full.txt, Line [696]-[697], still says its built-ins were verified against v10.1.1. Update the latter or clarify the scope so users do not receive mixed-version guidance.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@llms.txt` around lines 3 - 7, Synchronize the version claims between the
llms.txt introduction and the built-ins verification statement in llms-full.txt:
update the v10.1.1 reference near the built-ins documentation to match EPL
v10.2.0, or explicitly clarify that it refers to an older verification scope.
Ensure users are not presented with conflicting version guidance.
Points the highest-authority EPL properties at the official website for SEO/GEO discoverability.
[project.urls]Homepage → https://eplang.me (appears on the PyPI sidebar from the next release); addseplang,epl,english-programming-language,natural-languagekeywordsNo code changes; toml validated with tomllib.
Summary by CodeRabbit