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

[workflow-editor] Merge overlapping Codespaces-first guideline sections

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#4,533 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
63/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions
Área
documentation

Línea de trabajo

Lee .github/workflows/guidelines.md y compara las cuatro secciones mencionadas sobre Codespaces-first con la propuesta ## Codespaces-first core route de cinco viñetas. Comprueba cómo los siete archivos de workflow enumerados importan las directrices compartidas y, después, valida esos workflows con --validate. La tarea estará terminada cuando se hayan consolidado las secciones que se solapan, se conserven todas las directrices distintas y la validación se complete correctamente sin cambios en los archivos lock.

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

Descripción

agentic-workflows documentation workflow-editor

[!CAUTION]
Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: .github/workflows/guidelines.md

What changed

.github/workflows/guidelines.md is the shared authoring reference imported by seven other workflow files (guidelines-enforcer.md, security-side-quest.md, side-quest.md, workshop-author.md, workshop-explanatory-diagrams.md, workshop-skill-activity-author.md, workshop-ui-screenshots.md). It had grown four small, overlapping sections that all said variations of "keep the core route in Codespaces, delay gh setup":

  • ## Codespaces-first tooling progression
  • ## Codespaces-first instruction design
  • ## Prerequisite discipline
  • ## Learner empathy

Each repeated the same underlying rule (stay in Codespaces, don't front-load gh/prerequisites, be patient with terminal-new learners) with slightly different wording, forcing readers to cross-reference four headings for one idea.

Why this is more Skills-like

Merged the four sections into a single ## Codespaces-first core route section with five tight, non-redundant bullets. This mirrors GitHub Skills' direct, no-repeat instructional style — one clear heading per concept instead of near-duplicate guidance spread across several short sections. No rule was dropped; each distinct point (Codespaces-only route, delayed gh setup, prerequisite discipline, learner empathy, UI-first dispatch) is still present, just consolidated.

Validation

  • guidelines.md has no frontmatter and isn't itself a compiled workflow, so there's no lock file to regenerate for it.
  • Compiled all seven workflows that reference guidelines.md with --validate; all compiled successfully. The generated .lock.yml content was unaffected (confirmed via diff), since guidelines.md is read as supporting instruction text at agent runtime, not embedded at compile time — so no lock file changes are included in this PR.

[!WARNING]

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • registry.npmjs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by ✂️ Workflow Skills Editor · copilot · auto · 78.2 AIC · ⌖ 8.61 AIC · ⊞ 9.6K · ◷

  • expires on Oct 14, 2026, 7:51 AM UTC

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

Original error: The process '/usr/bin/git' failed with exit code 1

Workflow Run: View run details and download bundle artifact

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

Create the pull request manually 
# Download the artifact from the workflow run
gh run download '38364624118' -n agent -D '/tmp/agent-38364624118'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-38364624118/aw-workflow-editor-merge-codespaces-guidance.bundle'
temp_ref='refs/bundles/create-pr-workflow-editor-merge-codespaces-guidance-dbe6d087db6e583b-e0649b81'
target_ref='refs/heads/workflow-editor/merge-codespaces-guidance-dbe6d087db6e583b'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
  bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
  echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
  exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'workflow-editor/merge-codespaces-guidance-dbe6d087db6e583b'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"

# Push the branch to the target remote
git push 'origin' 'workflow-editor/merge-codespaces-guidance-dbe6d087db6e583b'

# Create the pull request
gh pr create --title '[workflow-editor] Merge overlapping Codespaces-first guideline sections' --base 'main' --head 'workflow-editor/merge-codespaces-guidance-dbe6d087db6e583b' --repo 'githubnext/gh-aw-workshop'
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
1 d 5 h
PR fusionados (30 d)
16

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin 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/gh-aw-workshop

Todos los issues de githubnext/gh-aw-workshop

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.