Supporting external tools #79
Replies: 2 comments 1 reply
-
|
Nice workflow! GitHub Pages would be perfect for this - could auto-update when main changes and showcase all the customizations with search/filtering. I like a simple search index and it would make it easy for us to find specific instructions/prompts by category or language. |
Beta Was this translation helpful? Give feedback.
-
|
Late to the party... I maintain an index of the instructions here: https://pez.github.io/awesome-copilot-index/index.html (I have not updated it to include Collections yet, but will probably do this at some point.) It is polling this repo, and I guess it could be done via web-hook instead. I'll have a look at how to do this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As this repo has grown, discoverability is a critical challenge that we need to tackle; I talked about it in this discussion.
While we could build tooling ourselves, the community is already out there building awesome experiences and we want to make it easier for them.
One way to support this is we're looking to add a workflow to the repo that will support invoking a webhook when changes are merged to
main. Here is the PR that I'm iterating on.If you have a tool that you want to have notified when the repo is updated, reach out with the webhook that you want to have invoked, and we'll add it to the list.
Note - the webhooks are going to be kept in a secret in the repo, rather than the workflow file, so that we can better ensure the privacy of others platforms, meaning you can have an authentication key in the URL and it will be hidden in the job run.
Beta Was this translation helpful? Give feedback.
All reactions