github / github/app

Automations skill catalog does not refresh after a new top-level skill becomes available in the configured local checkout

未关闭
#3,278 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
没有语言数据
星标
2.1k
派生
153
PR 合并指标
30 天内没有已合并 PR

描述

## Confirmed scenario

GitHub Copilot App Automations says it can turn existing agent skills into automations and lists skills from a configured repository. A newly merged top-level skill (`skills/daily-brief`) did not appear: the page showed 48 older skills, and searching for `daily-bri` returned no matches, even though the current `master` contained 55 skills, including `skills/daily-brief`.

Automations builds its catalog from the configured project's local checkout/current working tree rather than directly from the repository's latest GitHub default branch. The skill needed to exist as a top-level repository skill such as `skills/daily-brief` in the configured checkout.

After the configured checkout was updated to current `master`, the page still remained stale until fully quitting the Copilot App with Cmd+Q and relaunching it. After relaunch, `daily-brief` appeared.

## Expected behavior

The Automations skill catalog should refresh automatically when the configured checkout changes, or provide an explicit Refresh/Reindex action and clearly explain that the catalog is sourced from the configured local checkout/current branch.

## Workaround

Update or switch the configured local checkout to the branch containing the skill, then fully quit and relaunch the App. No supported standalone cache-reset command was found; users should not need to delete internal cache databases.

## Environment

| Field | Value |
| --- | --- |
| App version | 1.1.14 |
| OS | macOS 26.6.2 |
| Theme | GitHub |
| Path | /workflows |
| Tenure | Week 2 |
| Observed | 2026-08-27 |

贡献指南

打开贡献指南

调研方向

使用已配置的本地 checkout 从 /workflows 页面复现:添加或更新一个顶层 skill,然后观察应用重启前后的目录。跟踪目录如何从已配置的 checkout 获取并刷新。完成标准是变更后的 skill 自动出现,或者提供明确的 Refresh/Reindex 操作和来源说明。

由索引模型根据 Issue 内容生成。

评估

领域
desktop, developer-experience
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
活跃
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。