[docs] docs: fix inconsistencies between doc/ and current source code
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 10/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- python
- Área
- documentation
Línea de trabajo
Review the listed files under doc/, including tool_usage_guide.md, analyze_check_versions.md, eng_sys_checks.md, request_builders.md, and the dev/ pages, against the referenced Python source and pipeline files. Start with the existing branch docs/fix-doc-inconsistencies-72041-bfbb16928a7b7e88 and verify each documented claim against the current implementation. Done means the documented commands, paths, names, versions, links, and workflows match the source without unrelated edits.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
[!TIP]
Your pull request is ready to create! 🎉 ✅Everything is OK—the changes have been pushed to branch
docs/fix-doc-inconsistencies-72041-bfbb16928a7b7e88. Please review the changes, including any protected files, before creating the pull request.The original pull request description is below.
Summary
Reviewed all markdown files under doc/ against the current source code (eng/tools/azure-sdk-tools, eng/scripts, sdk/core/azure-core, pipeline templates, etc.) and fixed the verifiable inconsistencies found. No unrelated changes were made.
Fixes
doc/tool_usage_guide.md: Theazpysdkcommand table was missing several existing subcommands. Added rows forwhl,whl_no_aio,sdist,mindependency,latestdependency, andchangelog(all confirmed present ineng/tools/azure-sdk-tools/azpysdk/main.py).doc/analyze_check_versions.md: Fixed a malformed Markdown table (rows were missing their leading|), and corrected the Pylint Guidelines Checker "Next Version" from0.5.7to0.5.9to matchNEXT_PYLINT_GUIDELINES_CHECKER_VERSIONineng/tools/azure-sdk-tools/azpysdk/pylint.py.doc/eng_sys_checks.md: Corrected claims thatmindependencyruns in PR/Nightly/Release builds. It is currently commented out of bothPR_BUILD_SETandFULL_BUILD_SETineng/scripts/set_checks.pypending CFS onboarding (tracked in #48346); added a note pointing to the tracking issue.doc/request_builders.md: Fixedresponse.texttoresponse.text()—HttpResponse.textis a method (seeazure/core/rest/_rest_py3.py/_http_response_impl.py), not a property. (This already matched correctly in the siblingdoc/send_request.md.)doc/dev/perfstress_tests.md: Fixed a stale install path for thesystemperfextra.devtools_testutils(and itssystemperfextra) now live undereng/tools/azure-sdk-tools, nottools/devtools_testutils.doc/dev/conda-builds.md: Replaced an instruction to manually edit a nonexistenteng/conda_env.ymlfile with an accurate description of the automatedconda-update-pipeline.yml/conda/update_conda_files.pyflow (the real version file lives atconda/conda-recipes/conda_env.ymland is already documented correctly indoc/dev/conda-release-dev.md).doc/dev/mgmt/tests.md: Fixed stale function/class names to match current source ineng/tools/azure-sdk-tools/devtools_testutils/mgmt_settings_fake.pyandmgmt_recorded_testcase.py:get_azure_core_credential()→get_azure_core_credentials()get_credential()→get_credentials()AzureTestCase→AzureMgmtRecordedTestCase
Verification
- Checked every relative Markdown link/image reference under
doc/resolves to an existing file (no broken internal links remain beyond one pre-existing regex snippet inside a code block that is not an actual link). - Cross-referenced tool/version/command claims against the current implementation in
eng/tools/azure-sdk-tools/azpysdk/*.py,eng/scripts/set_checks.py, andsdk/core/azure-core. - Reviewed
doc/dev/mgmt/*,doc/dev/conda-*,doc/dev/ai/*, and the remaining top-leveldoc/*.mdfiles; no further verifiable inconsistencies were found (the rest of the documentation matches current tooling, e.g.azpysdk-based workflows,pyproject.toml-based packaging, and Chronus changelog usage).
[!NOTE]
GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch
docs/fix-doc-inconsistencies-72041-bfbb16928a7b7e88and are ready to review.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (38 of 186 lines)
From 07a9db1d2c399c7d35965425c7e7b56d9fb58c10 Mon Sep 17 00:00:00 2001
X-GH-AW-Base-Commit: 1053b0652a66b30d3d51844320b54af22600b50b
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 28 Sep 2026 05:07:36 +0000
Subject: [PATCH] docs: fix inconsistencies between doc/ and current source
code
- tool_usage_guide.md: add missing azpysdk commands to the tool table
(whl, whl_no_aio, sdist, mindependency, latestdependency, changelog)
- analyze_check_versions.md: fix malformed table (missing leading `|`)
and correct the Pylint Guidelines Checker "Next Version" (0.5.7 ->
0.5.9, matching NEXT_PYLINT_GUIDELINES_CHECKER_VERSION in pylint.py)
- eng_sys_checks.md: correct references to `mindependency` running in
PR/Nightly/Release builds -- it is currently commented out of
PR_BUILD_SET/FULL_BUILD_SET in eng/scripts/set_checks.py pending
CFS onboarding (issue #48346)
- request_builders.md: fix `response.text` to `response.text()`, since
HttpResponse.text is a method, not a property (see azure-core's
azure/core/rest/_rest_py3.py)
- dev/perfstress_tests.md: fix stale install path for the `systemperf`
extra; it lives at eng/tools/azure-sdk-tools[systemperf], not
tools/devtools_testutils[systemperf]
- dev/conda-builds.md: replace the stale manual instruction to edit a
nonexistent eng/conda_env.yml with an accurate description of the
automated conda-update-pipeline.yml / update_conda_files.py flow
- dev/mgmt/tests.md: fix function/class name typos
(get_azure_core_credential -> get_azure_core_credentials,
get_credential -> get_credentials, AzureTestCase ->
AzureMgmtRecordedTestCase) to match
devtools_testutils/mgmt_settings_fake.py and mgmt_recorded_testcase.py
Co-authored-by: Copilot <[email protected]>
---
doc/analyze_check_versions.md | 12 ++++++------
doc/dev/conda-builds.md | 2 +-
doc/dev/mgmt/tests.md | 10 +++++-----
doc/dev/perfstress_tests.md | 2 +-
doc/eng_sys_ch
... (truncated)
Generated by Documentation Consistency Check · copilot · sonnet50 · 500.9 AIC · ⌖ 6.8 AIC · ⊞ 7.7K · ◷
- Lenguaje dominante
- Python
- Estrellas
- 5.6k
- Forks
- 3.4k
- Merge medio
- 1 d 18 h
- PR fusionados (30 d)
- 214
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Azure/azure-sdk-for-python
-
Evaluation Service Attention
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Azure/azure-sdk-for-python#49190 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Update CODEOWNERSAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Azure/azure-sdk-for-python#49183 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Evaluation Service Attention
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Azure/azure-sdk-for-python#49153 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Search Service Attention
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Azure/azure-sdk-for-python#48555 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Azure.Core customer-reported feature-request needs-team-attention
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Azure/azure-sdk-for-python#47186 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Azure/azure-sdk-for-python
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
letsencrypt/cp-cps#353 ·
-
Marble Madness II is missingAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
PedestrianDynamics/pyFDS-Evac#394 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
DOI-USGS/pywatershed#421 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
python-pillow/Pillow#10087 · 1 comentario ·
Los mantenedores suelen responder en 1 día