Not all feather icons are supported by actions

[rachmari]

The new questionnaire allows you to choose unsupported feather icons. If the documentation is correct, I don't think we support these icons:

chrome
codepen
coffee
figma
frown
github
gitlab
instagram
key
linkedin
meh
mouse-pointer
pen-tool
slack
smile
trello
twitter
x-octagon
youtube

The documentation over here lists the icons that are supported right now.

[JasonEtco]

That's true, thanks for opening this @rachmari! We can filter those out in the script that generates the .json file pretty easily. However, I'm concerned with getting the list of icons that GitHub does not support 🤔 We could go so far as to parse the doc site, but that's a little dicey.

cc @macklinu ✨

[gr2m]

We could go so far as to parse the doc site, but that's a little dicey

Oh I gotcha, I did this so often now, happy to help. We could create a separate package that returns all supported GitHub Action icons and auto-updates. It would be similar to octokit/webhooks, just one document page that a script would call and turn into JSON, then create a PR if something changed during a nightly cron job

[macklinu]

We could create a separate package that returns all supported GitHub Action icons and auto-updates. It would be similar to octokit/webhooks, just one document page that a script would call and turn into JSON, then create a PR if something changed during a nightly cron job

I like that approach. This is something that came up initially in #57 (see #57 (comment) for some history) but ended up choosing the official feather-icons icon names list vs. parsing the GitHub Actions site. However, I think running a nightly cron job to keep supported icon names up to date sounds good - let me know if I can help with that here or in another repo. 👍

[JasonEtco]

Thanks for the suggestions y'all ❤️

running a nightly cron job to keep supported icon names up to date sounds good - let me know if I can help with that here or in another repo.

If we go down that route, definitely in favor of it being a separate repo (potentially as a GitHub Action 😱)

[gr2m]

+1 for separate repo, this might be useful to others, too. And besides publishing to npm, you could also publish the JSON to GitHub pages so non-npm tools could easily load a machine-readable format. I do that for octokit/routes: https://octokit.github.io/routes/

[alex-page]

I have updated the links in the hope that won't cause confusion.

[github-actions]

This issue has been inactive for awhile; please comment if it's still relevant!