Skip to content

docs: broken link to tour-github-issues.md in tour-first-session.md #610

Closed

Description

@diberry

Broken link in tour-first-session.md

File: docs/src/content/docs/tour-first-session.md (line 263)
Link text: "GitHub Issues Walkthrough"
Target: tour-github-issues.md
Problem: The target file does not exist. Only tour-gitlab-issues.md exists in the same directory.

How to reproduce

�ash npm test -- --reporter verbose test/docs-links.test.ts

The docs-links.test.ts link checker catches this:

docs/src/content/docs/tour-first-session.md:263 - Link to "tour-github-issues.md" does not exist (text: "GitHub Issues Walkthrough")

Possible fixes

  1. Create docs/src/content/docs/tour-github-issues.md (a GitHub Issues walkthrough page)
  2. Or update the link to point to an existing page (e.g., remove the link, or point to the scenarios section)

Context

This is pre-existing on the dev branch — the file tour-first-session.md has not been modified by any recent PRs. It's currently blocking CI on PR #11 (TypeDoc API reference) even though that PR didn't introduce the broken link.

The link is currently being added to KNOWN_ISSUES in docs-links.test.ts as a workaround so PR #11 can pass CI independently.

Activity

  1. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    📋 Assigned to PAO (DevRel)

    Issue: #610 — docs: broken link to tour-github-issues.md in tour-first-session.md

    PAO will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    PAO, work on issue #610

  2. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #610 — docs: broken link to tour-github-issues.md in tour-first-session.md
    Assigned to: FIDO (Quality Owner)
    Reason: Issue relates to testing/quality work

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  3. bradygaster commented on Mar 26, 2026

    @bradygaster
    Collaborator

    Triage: Broken docs link. Routing to PAO (docs) for quick fix.

  4. added a commit that references this issue on Mar 26, 2026
    1ab2f5c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsgo:needs-researchNeeds investigationpriority:p1This sprintsquadSquad triage inbox — Lead will assign to a member

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions