docs: FAQ table links still point at pre-AMP anchors in lib/crewai/README.md

Abierto
  • ¿Algo no está bien?
#9,243 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@TejasLamba2006 ya está trabajando en esto.

Desde el 9/11/2026.

  • #9244 de @severus0044 — cerrado sin fusionar
  • #9303 de @TejasLamba2006 — abierto

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
60.6k
Forks
9.1k
Merge medio
1 d 4 h
PR fusionados (30 d)
214

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de crewAIInc/crewAI

Todos los issues de crewAIInc/crewAI

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.