Skip to content

docs: add agent-assisted import & adapt section to packaging-imports guide#24397

Merged
pelikhan merged 1 commit intomainfrom
copilot/add-agent-import-workflow-section
Apr 3, 2026
Merged

docs: add agent-assisted import & adapt section to packaging-imports guide#24397
pelikhan merged 1 commit intomainfrom
copilot/add-agent-import-workflow-section

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 3, 2026

The packaging-imports guide covered gh aw add/gh aw add-wizard but had no guidance for using a coding agent to import and heavily customize a workflow from another repo in an uninitialised repository.

Changes

  • packaging-imports.md.mdx — renamed to enable the <Tabs> Starlight component
  • New section: "Using an Agent to Import and Adapt a Workflow" — inserted after "Adding Workflows", covering:
    • GitHub Web Interface — three tabbed prompt examples (Daily Status Report, Issue Triage, CI Doctor), each starting with install.md initialization since the repo is assumed uninitialised
    • Coding Agent — step-by-step walkthrough with a generic SOURCE_WORKFLOW/OWNER/REPO prompt template, matching the style of creating-workflows.mdx

Prompt style mirrors creating-workflows.mdx: install.md URL for init, then an adapt instruction with concrete source URL and customization guidance.

Initialize this repository for GitHub Agentic Workflows using https://raw.githubusercontent.com/github/gh-aw/main/install.md

Then import and adapt the SOURCE_WORKFLOW workflow from OWNER/REPO. The source is at
https://github.com/OWNER/REPO/blob/main/workflows/SOURCE_WORKFLOW.md.

Adapt the workflow for this repository: update any labels, assignees, branch names, and
permissions to match this project's structure. Keep the overall purpose and logic intact.

Convert packaging-imports.md to .mdx and add a new "Using an Agent
to Import and Adapt a Workflow" section. The section follows the same
prompt style as the Creating Workflows page, with tabbed examples for
the GitHub Web Interface and a step-by-step coding agent workflow.
All prompts include repository initialization via install.md since
the repo is assumed to be uninitialised.

Agent-Logs-Url: https://github.com/github/gh-aw/sessions/76c6bcbf-0914-44ea-9d1a-d671466ad8a6

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
@pelikhan pelikhan marked this pull request as ready for review April 3, 2026 23:12
Copilot AI review requested due to automatic review settings April 3, 2026 23:13
@pelikhan pelikhan merged commit e3c1c27 into main Apr 3, 2026
1 check passed
@pelikhan pelikhan deleted the copilot/add-agent-import-workflow-section branch April 3, 2026 23:13
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates documentation to describe how to use a coding agent (or GitHub web Copilot) to import an existing workflow from another repository and adapt it in a new/uninitialized repo, and refreshes the Agent Factory status page schedules.

Changes:

  • Convert the packaging imports guide to MDX to use Starlight <Tabs> and add a new “Using an Agent to Import and Adapt a Workflow” section with prompt templates.
  • Add tabbed GitHub web prompts (Daily Status Report / Issue Triage / CI Doctor) and a generic “Coding Agent” step-by-step template.
  • Update the Agent Factory status table with revised schedule strings and add entries for token optimizer/usage analyzer workflows.
Show a summary per file
File Description
docs/src/content/docs/guides/packaging-imports.mdx Adds an agent-assisted import/adapt section and prompt templates using Starlight Tabs.
docs/src/content/docs/agent-factory-status.mdx Updates workflow schedule strings and adds new workflow rows to the status table.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (2)

docs/src/content/docs/guides/packaging-imports.mdx:82

  • The “Issue Triage” tab prompt asks the agent to “find a suitable issue triage workflow in github/gh-aw” but doesn’t provide a concrete source URL/path. Since gh-aw’s workflow specs live under .github/workflows/ (not workflows/), this prompt is ambiguous and may send users searching the wrong location. Consider pointing to a specific workflow (e.g., .../blob/main/.github/workflows/issue-triage-agent.md or auto-triage-issues.md) to make the example immediately actionable and consistent with the other tabs.

This issue also appears on line 103 of the same file.
docs/src/content/docs/guides/packaging-imports.mdx:110

  • The generic prompt template hard-codes the source location as .../blob/main/workflows/SOURCE_WORKFLOW.md, but many repos (including this one) store workflow specs under .github/workflows/. This can lead to broken URLs and confusion when users follow the template. Consider changing the placeholders to include a PATH (e.g., PATH/TO/WORKFLOW.md) or explicitly call out both common locations (workflows/ and .github/workflows/) in the template text.
  • Files reviewed: 2/2 changed files
  • Comments generated: 0

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.

3 participants