Skip to content

docs: fix hardcoded absolute paths in prompt files - #1718

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/fix-prompt-absolute-paths-bd1eda9632eef279
Draft

docs: fix hardcoded absolute paths in prompt files#1718
github-actions[bot] wants to merge 1 commit into
mainfrom
docs/fix-prompt-absolute-paths-bd1eda9632eef279

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Agent Documentation Update

Findings

Area Issue File(s)
accuracy All three authoring prompt files reference prompt-contract.md and the docs/ pages using hardcoded absolute paths specific to the CI runner environment (/home/runner/work/ado-aw/ado-aw/). These paths are broken in every other context: local development, agents using the skills via raw GitHub URL download, and any other workspace. prompts/create-ado-agentic-workflow.md, prompts/debug-ado-agentic-workflow.md, prompts/update-ado-agentic-workflow.md

Applied Fixes

  • Replaced /home/runner/work/ado-aw/ado-aw/prompts/prompt-contract.md./prompt-contract.md in all three prompts
  • Replaced /home/runner/work/ado-aw/ado-aw/docs/<page>.mddocs/<page>.md in all reference lists

Notes

Verified by searching for /home/runner across prompts/*.md. The prompts/ files are fetched via version-pinned raw GitHub URLs by the Agency/Copilot skill files (agency/plugins/ado-aw/skills/*/SKILL.md) and executed in consumer repo environments where the old paths cannot possibly resolve. Repo-relative paths (docs/front-matter.md, ./prompt-contract.md) work for agents operating in the ado-aw repo directly; for consumer repo contexts the MCP tools (catalog, lint_workflow, etc.) already supply the necessary context.


Created by the agent-documentation maintainer workflow.

Generated by Agent Documentation Maintainer · 96.6 AIC · ⌖ 12.3 AIC · ⊞ 8.7K ·

Replace environment-specific /home/runner/work/ado-aw/ado-aw/ prefixes
with repo-relative paths in all three authoring prompt files. The old
paths only resolved on the CI runner; agents using these prompts in
any other environment (local dev, skill downloads) would get broken
file references.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants