Skip to content

Migrate inline repo-memory configs to shared/repo-memory-standard.md#29397

Closed
Copilot wants to merge 3 commits into
mainfrom
copilot/refactor-inline-repo-memory-config
Closed

Migrate inline repo-memory configs to shared/repo-memory-standard.md#29397
Copilot wants to merge 3 commits into
mainfrom
copilot/refactor-inline-repo-memory-config

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 30, 2026

19 workflows defined repo-memory: inline, each slightly differently. This caused configuration drift and made centralised changes (e.g. default file-glob, size limits) harder to apply uniformly.

Migrated (4 workflows)

Replaced inline tools.repo-memory: blocks with the shared import, passing non-default values as inputs where needed:

Workflow Override
workflow-health-manager.md max-patch-size: 51200
copilot-cli-deep-research.md max-file-size: 204800
agent-performance-analyzer.md
pr-triage-agent.md

Before:

tools:
  repo-memory:
    branch-name: memory/pr-triage
    file-glob: "**"
    max-file-size: 102400

After:

imports:
  - uses: shared/repo-memory-standard.md
    with:
      branch-name: "memory/pr-triage"
      description: "Historical PR triage data and categorization results"

Kept inline with documented reason (15 workflows)

Added # non-standard: comments to each remaining workflow explaining why the shared component can't be used:

  • wiki: truedaily-community-attribution, weekly-blog-post-writer, technical-doc-writer, glossary-maintainer, developer-docs-consolidator
  • branch-prefix: (daily rotation)daily-code-metrics, daily-sentrux-report
  • Campaign-specific globsecurity-compliance, code-scanning-fixer
  • .txt in file-globdaily-cli-performance, daily-testify-uber-super-expert
  • max-file-count: not in standardfirewall-escape
  • Intentional .md-only restrictiondeep-report, smoke-ci
  • Subdirectory-scoped globmetrics-collector

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://api.github.com/graphql
    • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw (http block)
    • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw e8oqgmxoiVP4 (http block)
    • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw -pack /home/REDACTED/work/gh-aw/gh-aw/cmd/gh-aw/main.go (http block)
  • https://api.github.com/repos/actions/checkout/git/ref/tags/v6
    • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v6 --jq [.object.sha, .object.type] | @tsv (http block)
    • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v6 --jq [.object.sha, .object.type] | @tsv ory-config (http block)
    • Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v6 --jq [.object.sha, .object.type] | @tsv ory-config repo-memory: r: $owner, name: $name) { hasDiscussionsEnabled } } (http block)
  • https://api.github.com/repos/actions/setup-node/git/ref/tags/v6
    • Triggering command: /usr/bin/gh gh api /repos/actions/setup-node/git/ref/tags/v6 --jq [.object.sha, .object.type] | @tsv (http block)
    • Triggering command: /usr/bin/gh gh api /repos/actions/setup-node/git/ref/tags/v6 --jq [.object.sha, .object.type] | @tsv ory-config repo-memory: yml (http block)
    • Triggering command: `/usr/bin/gh gh api /repos/actions/setup-node/git/ref/tags/v6 --jq [.object.sha, .object.type] | @TSV report.md rd.md and document non-standard configs

Agent-Logs-Url: REDACTED 64/bin/go GOINSECURE GOMOD GOMODCACHE go env cs-collector.md GO111MODULE ache/go/1.25.8/x64/bin/go GOINSECURE GOMOD GOMODCACHE go` (http block)

  • https://api.github.com/repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b
    • Triggering command: /usr/bin/gh gh api /repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b --jq [.object.sha, .object.type] | @tsv (http block)
    • Triggering command: /usr/bin/gh gh api /repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b --jq [.object.sha, .object.type] | @tsv ity-compliance.lock.yml GO111MODULE 1/x64/bin/git GOINSECURE GOMOD GOMODCACHE go env low-health-managOUTPUT GO111MODULE ache/go/1.25.8/x168.63.129.16 GOINSECURE GOMOD GOMODCACHE go (http block)
    • Triggering command: /usr/bin/gh gh api /repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b --jq [.object.sha, .object.type] | @tsv ity-compliance.md GO111MODULE ache/go/1.25.8/x64/bin/go GOINSECURE GOMOD GOMODCACHE go env low-health-manag-nxv GO111MODULE ache/go/1.25.8/x64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
  • https://api.github.com/repos/github/gh-aw
    • Triggering command: /usr/bin/gh gh api /repos/github/gh-aw --jq .default_branch (http block)
    • Triggering command: /usr/bin/gh gh api /repos/github/gh-aw --jq .default_branch 4fe762b6:.github/workflows/technical-doc-writer.lock.yml GO111MODULE /usr/local/sbin/git GOINSECURE GOMOD GOMODCACHE git comm�� 5409563f84e241f54fe762b6:.github-f Migrate 4 workflows to shared/reowner=github docker-compose GOSUMDB GOWORK 64/bin/go docker-compose (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI and others added 2 commits April 30, 2026 23:10
…n-standard configs

Agent-Logs-Url: https://github.com/github/gh-aw/sessions/5f423899-5e43-4081-ae2b-e5244c8f2bc4

Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot AI changed the title [WIP] Refactor 19 workflows to adopt shared repo-memory configuration Migrate inline repo-memory configs to shared/repo-memory-standard.md Apr 30, 2026
Copilot AI requested a review from gh-aw-bot April 30, 2026 23:17
@pelikhan pelikhan closed this Apr 30, 2026
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.

[refactoring] Improve adoption of shared/repo-memory-standard.md — 19 workflows with inline repo-memory config

3 participants