Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
What I propose: To put each spoon in it's own repository. This gives following benefits: - Readme in markdown: screenshots, video, code examples, etc. - Gives visibility of which spoons are popular by being able to star a repo. - Release management. With a simple gh-action it's possible to setup automated releases. Gh-action generates a .zip with a .spoon inside. Each new version can be simply downloaded from the releases page of the repository. - Updates. With github releases it's possbile to check if there is a new version of the spoon. Here is an example function. - Maybe this will simplify life of hammerspoon maintainers? 😄 Spoons will be created by community only, so you don't need to maintain the /spoons repository anymore.
You can find some examples here: - /gitlab-merge-requests.spoon. - /spotify-search-and-play.spoon.
This is crossposted from this issue: https://github.com/Hammerspoon/Spoons/issues/255.