rename yeagerai to genlayerlabs#235
Conversation
✅ Deploy Preview for genlayer-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughThis update replaces all references to "YeagerAI" and the "yeagerai" GitHub organization with "GenLayer Labs" and "genlayerlabs" across the project. It updates URLs, license attributions, and partner metadata, removes Yeager AI partner references, and introduces GenLayer Labs as the new core partner in documentation and metadata. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Documentation
participant GitHub
User->>Documentation: Clicks on a project/resource link
Documentation->>GitHub: Redirects to genlayerlabs repository
GitHub-->>User: Displays the requested resource under genlayerlabs
Poem
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (7)
package.json (1)
13-20: URLs updated correctly – consider aligning theauthorfieldThe repository, bugs and homepage links now point to
genlayerlabs– LGTM.
Small nit: theauthoris still"GenLayer". If the brand is now “GenLayer Labs”, update for consistency:- "author": "GenLayer", + "author": "GenLayer Labs",pages/developers/intelligent-contracts/examples/wizard-of-coin.mdx (1)
61-61: URL update ok – markdown style tipThe trailing “)” is fine, but adding a descriptive link title can improve accessibility:
-You can check out this code on our [GitHub](https://github.com/genlayerlabs/genlayer-simulator/blob/main/examples/contracts/wizard_of_coin.py) +You can check out this code on [GitHub – wizard_of_coin.py](https://github.com/genlayerlabs/genlayer-simulator/blob/main/examples/contracts/wizard_of_coin.py)pages/partners/_meta.json (1)
2-4: Confirm key ordering & duplication rules for partner dictionary
"genlayerlabs"was inserted at the top of the object.
If the build pipeline/en-site logic relies on alphabetical ordering (many static-site generators do), this could cause non-deterministic ordering or merge noise later on.{ - "genlayerlabs": "GenLayer Labs", - "heurist": "Heurist", - "ionet": "io.net" + "genlayerlabs": "GenLayer Labs", + "heurist": "Heurist", + "ionet": "io.net" }Double-check whether a sort or a linter rule is enforced before merging.
pages/developers/decentralized-applications/project-boilerplate.mdx (1)
55-58: Keep clone block in sync with call-outBoth occurrences were updated — looks good. Make sure any subsequent references (e.g., “fork on GitHub” badges) were likewise adjusted.
pages/partners/genlayerlabs.mdx (1)
1-6: Nit: trailing newline & markdown styleInsert a blank line after the final paragraph to satisfy markdown-lint rules and avoid concatenation when more content is appended.
pages/developers/intelligent-contracts/tooling-setup.mdx (2)
136-137: Link text updated; verify badge / image sourcesURL updated correctly. If any shields.io badges reference the old org, update them too.
144-145: Clone command: use.gitfor copy-paste parityMost users copy the line directly; appending
.gitavoids git fatal errors when pasting into some shells with strict URL parsing.- git clone https://github.com/genlayerlabs/genlayer-project-boilerplate.git + git clone https://github.com/genlayerlabs/genlayer-project-boilerplate.git
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (16)
LICENSES/MIT.txt(1 hunks)README.md(1 hunks)package.json(1 hunks)pages/api-references/genlayer-test.mdx(1 hunks)pages/developers/decentralized-applications/genlayer-js.mdx(1 hunks)pages/developers/decentralized-applications/project-boilerplate.mdx(2 hunks)pages/developers/intelligent-contracts/examples/prediction.mdx(1 hunks)pages/developers/intelligent-contracts/examples/wizard-of-coin.mdx(1 hunks)pages/developers/intelligent-contracts/tooling-setup.mdx(2 hunks)pages/developers/intelligent-contracts/tools/genlayer-cli.mdx(1 hunks)pages/developers/intelligent-contracts/tools/genlayer-studio/advanced-features/custom-plugins.mdx(2 hunks)pages/partners/_meta.json(1 hunks)pages/partners/genlayerlabs.mdx(1 hunks)pages/partners/yeager.mdx(0 hunks)pages/understand-genlayer-protocol/core-concepts/genvm.mdx(1 hunks)theme.config.tsx(1 hunks)
💤 Files with no reviewable changes (1)
- pages/partners/yeager.mdx
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - genlayer-docs
- GitHub Check: Header rules - genlayer-docs
- GitHub Check: Pages changed - genlayer-docs
🔇 Additional comments (12)
LICENSES/MIT.txt (1)
3-3: Confirm legal attribution remains accurateChanging the copyright holder to “GenLayer Labs” is reasonable given the re-branding, but make sure:
- The legal entity name is exactly the one that owns the IP.
- The year (“2024”) is still correct (update if the first public release under the new name happens in 2025+).
If both points are intentional, no further action needed.
package.json (1)
13-20: Scan for stray “yeagerai” referencesThese were the key JSON fields, but other hidden strings (README badges, scripts, comments) may still reference the old org.
Run the following quick check before merging:#!/bin/bash # Find any remaining lowercase 'yeagerai' tokens (case-insensitive, skip lock-files and node_modules) rg -i "yeagerai" --glob '!.git' --glob '!**/node_modules/**' --line-number --context 2pages/api-references/genlayer-test.mdx (1)
5-5: Doc link switched – looks goodLink now points to
genlayerlabs/genlayer-testing-suite. Verified path syntax is still valid.pages/developers/intelligent-contracts/tools/genlayer-studio/advanced-features/custom-plugins.mdx (2)
26-26: Reference path updated – LGTMThe protocol link now references the correct org. No issues spotted.
110-110: Schema link updated – LGTMConsistent with previous change.
pages/developers/intelligent-contracts/examples/prediction.mdx (1)
90-90: Validate that the new GitHub URL resolves correctlyThe reference now points at
genlayerlabs/genlayer-simulator. Please double-check the repo actually exists (and remains public) so readers don’t hit a 404.#!/bin/bash # Ensure the link returns HTTP 200 curl -s -o /dev/null -w "%{http_code}\n" https://github.com/genlayerlabs/genlayer-simulatortheme.config.tsx (1)
12-14: Confirm consistency of org-wide rebrand in config
project.linkanddocsRepositoryBasewere updated, but other hard-coded links (e.g., social cards, OG tags) still referencegenlayer.comor static assets.
No action needed if intentional; otherwise audit remaining constants for the old org.README.md (1)
15-17: License links updated – verify targets existGood catch updating the license paths. Quickly ensure the referenced files were actually renamed/moved in the repository so these links are not stale.
pages/understand-genlayer-protocol/core-concepts/genvm.mdx (1)
5-5: Link switched to new org – looks fineNothing else to flag.
pages/developers/decentralized-applications/genlayer-js.mdx (1)
75-78: Repository URL updated – LGTMChange is straightforward and correct.
pages/developers/intelligent-contracts/tools/genlayer-cli.mdx (1)
90-93: 👍 URL update looks correct — scan for staleyeageraireferencesThe new link (
github.com/genlayerlabs/genlayer-cli) resolves the org-rename.
Please run a quick repo sweep to ensure no staleyeagerai/genlayer-cliURLs remain in other docs.rg -n "yeagerai[/\-]genlayer-cli"pages/developers/decentralized-applications/project-boilerplate.mdx (1)
8-9: Good catch on the repo URLThe informational call-out now targets the correct org. Nothing else to add here.
| ## GenLayer Labs | ||
|
|
||
| [GenLayer Labs](https://www.genlayerlabs.com/) is a pioneering AI research lab dedicated to revolutionizing human-AI interaction. They are one of the core developers of GenLayer, focusing on using AI to enhance the performance, security, and scalability of blockchain networks. By embedding AI into the blockchain's core, GenLayer Labs enables decentralized applications to make smart decisions autonomously, opening new possibilities for automation and efficiency in various industries. | ||
|
|
||
| We encourage other developers and organizations to collaborate with GenLayer Labs on this groundbreaking project. Together, we can push the boundaries of what AI and blockchain technology can achieve. | ||
|
|
There was a problem hiding this comment.
Missing front-matter & slug may break routing
All other partner pages typically start with front-matter (e.g.:
---
title: GenLayer Labs
slug: /partners/genlayerlabs
---Without it, the page might not appear in navigation or could generate a duplicate H1.
Add the header to stay consistent.
🤖 Prompt for AI Agents
In pages/partners/genlayerlabs.mdx at the beginning of the file (lines 1 to 6),
the front-matter section with title and slug is missing, which can cause routing
issues and duplicate H1 headings. Add a front-matter block with title set to
"GenLayer Labs" and slug set to "/partners/genlayerlabs" at the top of the file
to ensure consistent navigation and proper page rendering.
2 participants
Summary by CodeRabbit