feat: add Node.js Agentic Issue Resolver to agents#613
feat: add Node.js Agentic Issue Resolver to agents#613Impesud wants to merge 6 commits intogithub:mainfrom
Conversation
Add documentation for Node.js Agentic Issue Resolver with key features and links.
aaronpowell
left a comment
There was a problem hiding this comment.
I'm not really sure that this makes sense as an agent, since it's a standalone sample. We are looking at the best way to support external samples in this repo, so I'll keep the PR open as we refine that
Thanks for the feedback, @aaronpowell ! I understand the distinction. I created this as a standalone repository to provide a complete, end-to-end example of a resilient agentic workflow. I'm happy to wait while you refine the structure for external samples. If you decide to create a 'Community Samples' or 'External Projects' section, I'd be glad to see this included there. Let me know if you need me to move the metadata file or adjust the description in the meantime! |
|
#632 is open to bring the cookbook across from the SDK repo, but I think we'll want a better way to list out external samples. @Impesud what's your thought on some kind of YAML file that external samples, such as yours, could be listed in and then we'll have a script that automates surfacing them in the repo? Or do you have other thoughts on how to surface them in the repo? |
Hi @aaronpowell , I think the YAML approach is the most scalable path forward. It turns this repository into a structured registry, making it easier for scripts to generate tables, galleries, or even a searchable site in the future. Here is a proposal for a schema that could live in a external-samples.yaml file: I am more than happy to be the first to adopt this format. If you decide to go this way, let me know if you'd like me to create the initial YAML file or if you have a specific location in mind for it. |
|
We could probably leverage https://github.com/github/awesome-copilot/blob/main/cookbook/cookbook.yml Let me have an experiment around with some structure |
That makes perfect sense, @aaronpowell . Leveraging cookbook.yml is a great way to maintain consistency across the repo. I'm ready to adapt my contribution once you’ve defined the new structure. Standing by for your updates! |
14d7f66 to
aaed079
Compare
ea85bbf to
4488150
Compare
Add a Community Samples cookbook section to cookbook.yml with the Node.js Agentic Issue Resolver as the first external recipe entry, linking to https://github.com/Impesud/nodejs-copilot-issue-resolver. Resolves the use case from PR #613 for supporting external samples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat(schema): add external recipe fields to cookbook schema Add optional external, url, and author fields to the recipe schema in cookbook.schema.json. When external is true, url is required via conditional validation. Author supports name (required) and url (optional) for attribution. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat(data): support external recipes in data generator - External recipes (external: true) skip local file validation - Validate URL format for external recipes - Pass through external, url, and author fields to output JSON - Add per-recipe languages array: derived from resolved variant keys for local recipes, and from tags matching known language IDs for external recipes - Collect language IDs in a first pass before processing recipes Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat(website): render external recipe cards on cookbook page - Extend Recipe interface with external, url, author, and languages - Render external recipes with Community badge, author attribution, and View on GitHub link instead of View Recipe/View Example buttons - Language filter uses per-recipe languages array uniformly - Remove Nerd Font icons from select dropdown options (native selects cannot render custom web fonts) - Add CSS for external recipe cards (dashed border, badge, author) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat(cookbook): add community samples section with first external recipe Add a Community Samples cookbook section to cookbook.yml with the Node.js Agentic Issue Resolver as the first external recipe entry, linking to https://github.com/Impesud/nodejs-copilot-issue-resolver. Resolves the use case from PR #613 for supporting external samples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat(cookbook): add Copilot SDK Web App to community samples Add aaronpowell/copilot-sdk-web-app — a full-stack chat app built with the GitHub Copilot SDK, .NET Aspire, and React. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Hi team! I'm submitting a new agentic sample.
This project provides a resilient implementation of a developer agent using the GitHub Copilot SDK, specifically optimized to handle the current Technical Preview limitations regarding file modifications.
Compliance:
Follows the AGENTS.md guidelines.
Includes frontmatter and proper file naming (.agent.md).
Moved to a standalone repo as recommended by @friggeri in the copilot-sdk repo.
Looking forward to your feedback!