spotify-search-and-play.spoon VS gitlab-merge-requests.spoon

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.

It uses hs.http to call Spotify's REST API and hs.chooser to display the options. You can get it here: https://github.com/fork-my-spoons/spotify-search-and-play.spoon

You can find some examples here: - /gitlab-merge-requests.spoon. - /spotify-search-and-play.spoon.

I think I can make a similar app, but you'll be able to customize the query path to the gitlabs's merge request endpoint (https://docs.gitlab.com/ee/api/merge_requests.html). So it will be possible to return any types of merge requests. If you think that it could be useful for you, please create an issue.