Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

chore(workflows): recompile safe-output fixtures with ado-aw v0.37.0

Abierto Apto para principiantes
  • ¿Algo no está bien?
#1,041 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
github-actions, rust
Área
build-system, ci-cd, testing-qa

Línea de trabajo

Comienza con los 27 archivos enumerados tests/safe-outputs/*.lock.yml y la ejecución del workflow recompile-safe-output-fixtures enlazada en el issue. Descarga el artefacto del agente, inspecciona la rama generada y ejecuta ado-aw check contra cada archivo lock. Se considera terminado cuando las 27 comprobaciones pasan y el diff se limita a los archivos lock enumerados, sin cambios en archivos .md de origen.

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

Descripción

agentic-workflows

Recompile tests/safe-outputs/ against ado-aw v0.37.0

Bumps the version field in every tests/safe-outputs/*.lock.yml metadata marker from 0.35.3 to 0.37.0, picking up any compile-output changes shipped in ado-aw v0.37.0.

Pre-flight integrity check

Before recompiling, ado-aw check was run against every existing lock file using the released v0.37.0 binary:

  • Integrity failures: 27 of 27 files
tests/safe-outputs/add-build-tag.lock.yml
tests/safe-outputs/add-pr-comment.lock.yml
tests/safe-outputs/azure-cli.lock.yml
tests/safe-outputs/comment-on-work-item.lock.yml
tests/safe-outputs/create-branch.lock.yml
tests/safe-outputs/create-git-tag.lock.yml
tests/safe-outputs/create-pull-request.lock.yml
tests/safe-outputs/create-wiki-page.lock.yml
tests/safe-outputs/create-work-item.lock.yml
tests/safe-outputs/janitor.lock.yml
tests/safe-outputs/link-work-items.lock.yml
tests/safe-outputs/missing-data.lock.yml
tests/safe-outputs/missing-tool.lock.yml
tests/safe-outputs/noop-target.lock.yml
tests/safe-outputs/noop.lock.yml
tests/safe-outputs/queue-build.lock.yml
tests/safe-outputs/reply-to-pr-comment.lock.yml
tests/safe-outputs/report-incomplete.lock.yml
tests/safe-outputs/resolve-pr-thread.lock.yml
tests/safe-outputs/smoke-failure-reporter.lock.yml
tests/safe-outputs/submit-pr-review.lock.yml
tests/safe-outputs/update-pr.lock.yml
tests/safe-outputs/update-wiki-page.lock.yml
tests/safe-outputs/update-work-item.lock.yml
tests/safe-outputs/upload-build-attachment.lock.yml
tests/safe-outputs/upload-pipeline-artifact.lock.yml
tests/safe-outputs/upload-workitem-attachment.lock.yml
Files updated
tests/safe-outputs/add-build-tag.lock.yml
tests/safe-outputs/add-pr-comment.lock.yml
tests/safe-outputs/azure-cli.lock.yml
tests/safe-outputs/comment-on-work-item.lock.yml
tests/safe-outputs/create-branch.lock.yml
tests/safe-outputs/create-git-tag.lock.yml
tests/safe-outputs/create-pull-request.lock.yml
tests/safe-outputs/create-wiki-page.lock.yml
tests/safe-outputs/create-work-item.lock.yml
tests/safe-outputs/janitor.lock.yml
tests/safe-outputs/link-work-items.lock.yml
tests/safe-outputs/missing-data.lock.yml
tests/safe-outputs/missing-tool.lock.yml
tests/safe-outputs/noop-target.lock.yml
tests/safe-outputs/noop.lock.yml
tests/safe-outputs/queue-build.lock.yml
tests/safe-outputs/reply-to-pr-comment.lock.yml
tests/safe-outputs/report-incomplete.lock.yml
tests/safe-outputs/resolve-pr-thread.lock.yml
tests/safe-outputs/smoke-failure-reporter.lock.yml
tests/safe-outputs/submit-pr-review.lock.yml
tests/safe-outputs/update-pr.lock.yml
tests/safe-outputs/update-wiki-page.lock.yml
tests/safe-outputs/update-work-item.lock.yml
tests/safe-outputs/upload-build-attachment.lock.yml
tests/safe-outputs/upload-pipeline-artifact.lock.yml
tests/safe-outputs/upload-workitem-attachment.lock.yml
How this was produced
  • Downloaded ado-aw-linux-x64 from the v0.37.0 release and verified its SHA256 against checksums.txt.
  • Ran ado-aw check tests/safe-outputs/*.lock.yml against the released binary to detect drift (27/27 files failed).
  • Ran ado-aw compile --force on each tests/safe-outputs/*.md fixture from the repo root.
  • Re-ran ado-aw check against every regenerated lock file; all 27 passed.
  • The allowed-files glob in this workflow restricts the diff to tests/safe-outputs/**/*.lock.yml.
Reviewer checklist
  • Diff is limited to metadata markers (and any genuinely new compile output for v0.37.0).
  • No source .md fixture changes leaked in.
  • Daily smoke pipelines in the AgentPlayground sandbox stay green after merge.

This PR was opened automatically by the recompile-safe-output-fixtures workflow.

Generated by Recompile safe-output fixtures · 244.1 AIC · ⌖ 40.9 AIC · ⊞ 37.1K · ◷

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

To create a pull request with the changes:

# Download the artifact from the workflow run
gh run download 27575351721 -n agent -D /tmp/agent-27575351721

# Fetch the bundle into a temporary ref, then update the local branch
git fetch /tmp/agent-27575351721/aw-recompile-safe-outputs-v0.37.0.bundle refs/heads/recompile-safe-outputs-v0.37.0:refs/bundles/create-pr-recompile-safe-outputs-v0-37-0-376aaf7f1597ffa9-ee2394ee
git update-ref refs/heads/recompile-safe-outputs-v0.37.0-376aaf7f1597ffa9 refs/bundles/create-pr-recompile-safe-outputs-v0-37-0-376aaf7f1597ffa9-ee2394ee
git checkout recompile-safe-outputs-v0.37.0-376aaf7f1597ffa9
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d refs/bundles/create-pr-recompile-safe-outputs-v0-37-0-376aaf7f1597ffa9-ee2394ee

# Push the branch to origin
git push origin recompile-safe-outputs-v0.37.0-376aaf7f1597ffa9

# Create the pull request
gh pr create --title 'chore(workflows): recompile safe-output fixtures with ado-aw v0.37.0' --base main --head recompile-safe-outputs-v0.37.0-376aaf7f1597ffa9 --repo githubnext/ado-aw
Lenguaje dominante
Rust
Estrellas
27
Forks
8
Merge medio
3 d 18 h
PR fusionados (30 d)
10

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 githubnext/ado-aw

Todos los issues de githubnext/ado-aw

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.