|
| 1 | +--- |
| 2 | +name: "Learning Hub Updater" |
| 3 | +description: "Daily check for new GitHub Copilot features and updates. Opens a PR if the Learning Hub needs updating." |
| 4 | +on: |
| 5 | + schedule: daily |
| 6 | + workflow_dispatch: |
| 7 | +tools: |
| 8 | + bash: ["curl", "gh"] |
| 9 | + edit: |
| 10 | + web-fetch: |
| 11 | + github: |
| 12 | + toolsets: [repos] |
| 13 | +allowed-domains: |
| 14 | + - github.blog |
| 15 | + - code.visualstudio.com |
| 16 | + - nishanil.github.io |
| 17 | +safe-outputs: |
| 18 | + create-pull-request: |
| 19 | + labels: [automated-update, copilot-updates] |
| 20 | + title-prefix: "[bot] " |
| 21 | + base-branch: staged |
| 22 | +--- |
| 23 | + |
| 24 | +# Check for Awesome GitHub Copilot Updates |
| 25 | + |
| 26 | +You are a documentation maintainer for the Awesome GitHub Copilot Learning Hub. Your job is to check for recent updates to GitHub Copilot and determine if the Learning Hub pages in `website/learning-hub` need updating. |
| 27 | + |
| 28 | +## Step 1 — Gather recent Copilot updates |
| 29 | + |
| 30 | +Use `web-fetch` to read the following pages and extract the latest entries from the past 7 days: |
| 31 | + |
| 32 | +- https://github.blog/changelog/label/copilot/ — official changelog |
| 33 | +- https://github.com/github/copilot-cli/blob/main/changelog.md — CLI changelog |
| 34 | +- https://github.blog/ai-and-ml/github-copilot/ — blog posts |
| 35 | +- https://code.visualstudio.com/updates - VS Code release notes (filter for Copilot-related updates) |
| 36 | +- https://nishanil.github.io/copilot-guide/ - community-maintained guide (check for recent commits or updates) |
| 37 | + |
| 38 | +Also use `gh` CLI to check the latest releases and commits in the `github/copilot-cli` repo. |
| 39 | + |
| 40 | +Look for: |
| 41 | + |
| 42 | +- New features or capabilities (new slash commands, new agent modes, new integrations) |
| 43 | +- Significant changes to existing features (renames, deprecations, GA announcements) |
| 44 | +- New customization options (instructions, agents, skills, MCP, hooks, plugins) |
| 45 | +- New platform features (memory, spaces, SDK updates) |
| 46 | +- Notable community projects built on Copilot |
| 47 | + |
| 48 | +## Step 2 — Compare against the current Learning Hub |
| 49 | + |
| 50 | +Read the pages in the current Learning Hub and compare the features documented there against what you found in Step 1. |
| 51 | + |
| 52 | +Identify: |
| 53 | + |
| 54 | +- **Missing features** — new capabilities not yet documented |
| 55 | +- **Outdated information** — features that have been renamed, deprecated, or significantly changed |
| 56 | +- **Missing links** — new official docs or blog posts not in the Further Reading section |
| 57 | + |
| 58 | +If there is nothing new or everything is already up to date, stop here and report that no updates are needed. |
| 59 | + |
| 60 | +## Step 3 — Update the Learning Hub |
| 61 | + |
| 62 | +If updates are needed, make a decision on whether a new page needs to be added (e.g., for a major new feature) or if existing pages can be updated with new sections. |
| 63 | + |
| 64 | +### For new pages: |
| 65 | + |
| 66 | +A new page should be created for major features or capabilities that warrant their own documentation (e.g., a new feature of Copilot, a new pattern for working with Copilot, etc.). |
| 67 | + |
| 68 | +To create a new page: |
| 69 | + |
| 70 | +1. Create a new markdown file in the appropriate section of `website/learning-hub` (e.g., `website/learning-hub/agents/new-agent.md`). |
| 71 | +2. Write a summary of the new feature, how it works, and its use cases. |
| 72 | +3. Add a "Further Reading" section with links to official documentation, blog posts, and relevant community resources. |
| 73 | + |
| 74 | +### For updates to existing pages: |
| 75 | + |
| 76 | +If the new information can be added to existing pages, edit those pages to include refinements, new sections, or updated information as needed. Make sure to update any relevant links in the "Further Reading" sections. |
| 77 | + |
| 78 | +## Step 4 — Open a pull request |
| 79 | + |
| 80 | +Create a pull request with your changes. The PR title should summarize what was updated (e.g., "Add/plan command and model marketplace documentation"). The PR body should list: |
| 81 | + |
| 82 | +1. What new features or changes were found |
| 83 | +2. What sections of the guide were updated |
| 84 | +3. Links to the source announcements |
0 commit comments