docs: replace absolute runner paths with version-pinned URLs in prompt files - #1704
Draft
github-actions[bot] wants to merge 1 commit into
Draft
docs: replace absolute runner paths with version-pinned URLs in prompt files#1704github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…t files prompt-contract.md and the reference docs were referenced via /home/runner/work/ado-aw/ado-aw/... absolute paths. These paths only resolve on the githubnext/ado-aw GitHub Actions runner. Consumer repo agents that fetch the prompts via the version-pinned rawgithubusercontent URLs (as the agency/skills do) cannot access local absolute paths. Replace all absolute paths with the same version-pinned URL pattern used by the skill SKILL.md files, with x-release-please-version comments so release-please keeps them in sync with the compiler version. 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. |
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
prompt-contract.mdand the reference docs via/home/runner/work/ado-aw/ado-aw/...absolute paths. These paths only resolve on thegithubnext/ado-awGitHub Actions runner. Consumer repo agents that fetch the prompts via version-pinnedraw.githubusercontent.comURLs (as theagency/skills/files do) cannot access these local absolute paths, so the behavioral contract and reference docs are silently unreachable.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.mdwith a version-pinned URL in all three prompts/home/runner/work/ado-aw/ado-aw/docs/...reference paths with version-pinnedraw.githubusercontent.comURLs<!-- x-release-please-version -->comments to all new URLs so release-please keeps them in sync with the compiler version (matching the pattern already used inagency/plugins/ado-aw/skills/*/SKILL.md)Notes
The
agency/plugins/ado-aw/skills/create-workflow/SKILL.mdalready uses version-pinned URLs for fetching prompts (e.g.,https://raw.githubusercontent.com/githubnext/ado-aw/v0.45.1/prompts/create-ado-agentic-workflow.md). Those fetched prompts then referenced the contract and docs via absolute paths that don't exist in consumer repo environments. The fix brings the prompts into the same URL pattern the skills already use. All URLs verified against existing files in the repository at v0.45.1.Created by the agent-documentation maintainer workflow.