docs: add TakoAPI directory badge#2055
Conversation
|
|
Summary by CodeRabbit
WalkthroughA "Listed on TakoAPI" badge link is inserted into the ChangesTakoAPI Badge in README
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 Warning |
|
|
| Filename | Overview |
|---|---|
| README.md | Adds a TakoAPI badge, but it is placed inside a fenced bash code block, causing it to render as raw markdown text instead of a clickable badge image |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["README.md badge section (lines 9-16)\ndiv align center — existing badges render here"] -->|"should go here"| B["TakoAPI Badge\n[](takoapi.com)"]
C["Run Locally section (line 79)\nbash code block"] -->|"badge placed here (incorrect)"| D["Renders as raw text\n[](...)\ngit clone ..."]
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
README.md:79-84
Badge placed inside a fenced bash code block — it will not render as a clickable badge. Inside a fenced code block, GitHub renders content as raw text, so visitors will see the literal markdown syntax `[](...)` mixed into the "Run Locally" shell snippet instead of a visual badge. The badge should live outside the code block, ideally in the existing badge section at the top of the README.
```suggestion
```bash
# Clone and start
git clone https://github.com/Zipstack/unstract.git
```
Reviews (1): Last reviewed commit: "docs: add TakoAPI directory badge" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| ```bash | ||
| # Clone and start | ||
|
|
||
| [](https://takoapi.com/agents/zipstack-unstract) | ||
|
|
||
| git clone https://github.com/Zipstack/unstract.git |
There was a problem hiding this comment.
[](...) mixed into the "Run Locally" shell snippet instead of a visual badge. The badge should live outside the code block, ideally in the existing badge section at the top of the README.
| ```bash | |
| # Clone and start | |
| [](https://takoapi.com/agents/zipstack-unstract) | |
| git clone https://github.com/Zipstack/unstract.git | |
| ```bash | |
| # Clone and start | |
| git clone https://github.com/Zipstack/unstract.git |
Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 79-84
Comment:
Badge placed inside a fenced bash code block — it will not render as a clickable badge. Inside a fenced code block, GitHub renders content as raw text, so visitors will see the literal markdown syntax `[](...)` mixed into the "Run Locally" shell snippet instead of a visual badge. The badge should live outside the code block, ideally in the existing badge section at the top of the README.
```suggestion
```bash
# Clone and start
git clone https://github.com/Zipstack/unstract.git
```
How can I resolve this? If you propose a fix, please make it concise.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
79-87:⚠️ Potential issue | 🟠 Major | ⚡ Quick winBadge is placed inside a bash code fence and won't render as a clickable link.
The markdown badge syntax
[](...)on line 82 is nested within a bash code block (lines 79–87). Inside code fences, markdown syntax is not interpreted—it will display as literal text rather than as a rendered badge with a clickable hyperlink. Additionally, users copying this code block will inadvertently copy the badge markdown as part of their bash commands.The badge should be placed outside the code fence—either before the opening
\``bashor after the closing```` on line 87.🔧 Proposed fix: Move badge outside the code fence
### Run Locally ```bash -# Clone and start - -[](https://takoapi.com/agents/zipstack-unstract) - git clone https://github.com/Zipstack/unstract.git cd unstract ./run-platform.sh
+
Alternatively, place the badge **before** the code block if you prefer it to appear first: ```diff ### Run Locally +[](https://takoapi.com/agents/zipstack-unstract) + ```bash # Clone and start git clone https://github.com/Zipstack/unstract.git cd unstract ./run-platform.sh</details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.In
@README.mdaround lines 79 - 87, The markdown badge syntax for the TakoAPI
badge is currently nested inside the bash code fence and will not render as a
clickable link—instead it will display as literal text and be copied when users
execute the commands. Move the badge markdown outside the code fence by removing
it from between the openingbash and closingdelimiters, and place it
either before the code block (before the openingbash) or after the code block (after the closing) to ensure it renders properly as a clickable
badge.</details> <!-- cr-comment:v1:099dda6bf6c82a35d34db076 --> </blockquote></details> </blockquote></details>🤖 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. Outside diff comments: In `@README.md`: - Around line 79-87: The markdown badge syntax for the TakoAPI badge is currently nested inside the bash code fence and will not render as a clickable link—instead it will display as literal text and be copied when users execute the commands. Move the badge markdown outside the code fence by removing it from between the opening ```bash and closing ``` delimiters, and place it either before the code block (before the opening ```bash) or after the code block (after the closing ```) to ensure it renders properly as a clickable badge.
3 participants
Hi! 👋 unstract is listed in the TakoAPI open agent directory — a free, open catalog that helps people discover AI-agent projects ("one API to discover all agents").
Your listing: https://takoapi.com/agents/zipstack-unstract
This PR adds a small badge near the top of the README that links back to that listing, so visitors can find the directory entry. It's entirely optional — if you'd prefer not to include it, just close this PR (no hard feelings, and apologies for the noise).
No tracking and no obligations. Thanks for building unstract! 🙏