docs: FAQ table links still point at pre-AMP anchors in lib/crewai/README.md
维护者通常 1 天内回复
@TejasLamba2006 已经在做这个了。
开始于 2026年11月9日。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 35/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
调研方向
Open lib/crewai/README.md and inspect the three FAQ table links listed in the issue. Compare their fragments with the current AMP Q&A headings below the table. Done when all three links resolve to their matching headings; the issue reports a focused patch is already ready on a fork, and linked pull request #9244 is open.
由索引模型根据 Issue 内容生成。
描述
Description
Three links in the FAQ table of lib/crewai/README.md still use the old "CrewAI Enterprise" fragments, while the corresponding Q&A headings were renamed to "CrewAI AMP". Clicking them lands at the top of the page instead of the answer.
| Link text (unchanged) | Fragment now | Heading that exists |
|---|---|---|
| What additional features does CrewAI AMP offer? | #q-what-additional-features-does-crewai-enterprise-offer |
### Q: What additional features does CrewAI AMP offer? |
| Is CrewAI AMP available for cloud and on-premise deployments? | #q-is-crewai-enterprise-available-for-cloud-and-on-premise-deployments |
### Q: Is CrewAI AMP available for cloud and on-premise deployments? |
| Can I try CrewAI AMP for free? | #q-can-i-try-crewai-enterprise-for-free |
### Q: Can I try CrewAI AMP for free? |
Only the three #fragment parts need to change; link text and targets are correct.
Steps to reproduce
Open lib/crewai/README.md, jump to "Enterprise Features" in the FAQ, and click any of the three links. GitHub has no heading with the old slug, so the browser stays at the top of the document.
Expected behavior
Each link resolves to the matching ### Q: ... answer below the FAQ table (the slugs generated from the current AMP headings).
Verification
A heading-slug check over the current main file lists all three target headings with the AMP names and none with the Enterprise names; each stale fragment occurs exactly once.
I found this while auditing internal documentation links in high-star agent repositories. I have a focused three-line patch ready on a fork branch.
- 主要语言
- Python
- 星标
- 60.6k
- 派生
- 9.1k
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 218
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
crewAIInc/crewAI 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
feature-request
难度 2/5 1-3 小时 新手友好度 66/100
crewAIInc/crewAI#9200 · 1 条评论 ·
维护者通常 1 天内回复
-
[FEATURE] Docs: ApifyActorsTool example with a typed-input Actor可能已有人在做 @johnisanerd 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
crewAIInc/crewAI#9132 · 5 条评论 ·
维护者通常 1 天内回复
-
[BUG] Scrape tools reject the documented cookies mapping and drop cookies when the URL is passed at runtime可能已有人在做 @Luckyou-d 于 7 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
[BUG] OpenAI-compatible embedding model alias breaks embedder construction可能已有人在做 @gokay-ai 于 13 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
crewAIInc/crewAI#8761 · 1 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
question
难度 1/5 1 小时以内 新手友好度 68/100
vllm-project/vime#524 ·
维护者通常 7 天内回复
-
WOPI editor page is scrollable by a few pixels, which breaks scrolling in the document (Firefox)未关闭
难度 2/5 1-3 小时 新手友好度 84/100
suitenumerique/drive#969 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
theupdateframework/python-tuf#3044 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
FAIRmat-NFDI/pynxtools#861 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
NVIDIA/nsight-python#88 ·
维护者通常 1 天内回复