docs: fix hardcoded CI absolute paths in workflow-authoring prompts - #1706
Closed
github-actions[bot] wants to merge 1 commit into
Closed
docs: fix hardcoded CI absolute paths in workflow-authoring prompts#1706github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Replace /home/runner/work/ado-aw/ado-aw/ absolute paths with repo-root-relative paths in all three workflow-authoring prompts. The old paths were specific to the GitHub Actions runner environment and would break when agents consumed these prompts via the raw GitHub URL in any other context. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Collaborator
|
Closing as superseded by #1703, which fixed the hardcoded |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent Documentation Update
Findings
/home/runner/work/ado-aw/ado-aw/) from the GitHub Actions CI runner environment. These paths appear in theApply prompt-contract.mddirective and theReferencessection of each file. Agents consuming these prompts via raw GitHub URLs (as wired ininit-agent.md,init-skill.md, and the agency plugin) cannot resolve CI-local paths, breaking the cross-references entirely.prompts/create-ado-agentic-workflow.md,prompts/update-ado-agentic-workflow.md,prompts/debug-ado-agentic-workflow.mdApplied Fixes
Apply /home/runner/work/ado-aw/ado-aw/prompts/prompt-contract.md→Apply prompts/prompt-contract.mdin all three prompts/home/runner/work/ado-aw/ado-aw/docs/prefix →docs/in allReferencessections (8 paths total across 3 files)Notes
Verified against: the agent/skill templates in
src/data/init-agent.md,src/data/init-skill.md, andagency/plugins/ado-aw/reference these prompts viaraw.githubusercontent.comURLs, meaning agents fetch the raw file content and then must resolve the embedded paths relative to their repository checkout — not relative to the CI runner's filesystem. Repo-root-relative paths (prompts/prompt-contract.md,docs/front-matter.md, etc.) work correctly for any agent that has the repository checked out.No other documentation drift was found in this audit pass: AGENTS.md architecture tree matches the source layout, the docs index has no dead links, all safe-output tools are documented in
docs/safe-outputs.md, and CLI commands indocs/cli.mdmatchsrc/main.rs.Created by the agent-documentation maintainer workflow.