We're Joao and Tiago, and together we've built Slash Commands for GitHub to control your Issues and Pull Requests through your comments, which is available on GitHub Marketplace as of today [1].
As a bonus, we've also added a few pro features that we think you'll like:
- /giphy - Embed your favorite GIFs in your comments
- /merge-when-checks-green - will merge your Pull Request automatically after all your checks have succeeded
- /copy-metadata - Copies metadata (labels, asignees, etc...) from one Issue to another
Since this was built as a native GitHub app, all commands will work seamlessly with integrations such as the GitHub VSCode extension [2] and their CLI tool [3].
We've had a ton of fun building this project using Elixir and we want to continue improving it every day.
Looks nice but please allow an option to strip the commands from the actual issue afterwards. As the commands were made, it shouldn't clutter the body of the text.
project owner here, this is actually something that we took care in doing upfront so you should see the slash commands being stripped from the text body already.
If possible, could you refresh the page and check if they've been stripped please? Otherwise happy to take a better look at it if you'd kindly open an issue on https://github.com/slash-commands/feedback :)
I know about the scenario simulation, and when I have corresponded with the support team it is where they have pointed me. This in spite of saying I have read it and explained why it isn't doing what we're after.
In its current form, it is not adequate. We have to manually set up the resource to run it on. Once run, there is no easy reset, to re-run it (if, for example, the response was handled incorrectly).
It can be argued that mocking all behaviours should be carried out our side and not involve the GoCardless sandbox. I am open to that, but note we have not seen any existing libraries handling this.
And the behaviour of other payment processors suggests this is not the most common approach to take.
Edit: As samples of all events/payloads are not present, we have to record production data first in order to get the data we can use in our mocking and testing.
I would disagree or maybe we have different ideas of what recurring payments are. Most businesses that use recurring payments require their customers to allow them to ACH debit their account.
Are there a substantial number of macOS users using touchscreens?
EDIT: I don't know how I forgot about pinch to zoom via the trackpad. While my original question did start me down an interesting rabbit hole of touchscreen MacOS, I 100% agree that a lack of smooth pinch to zoom via the trackpad detracts from the overall user experience.
No macOS machines ship with touchscreens, but trackpad gestures are used heavily throughout macOS. I find pinch zooming on the Mac to feel pretty natural.
This feature is essential for mobile screens, and this is not meant to dismiss your concern, but what do you need pinch-to-zoom for on desktop? Everything is already huge and readable on desktop.
Sure, I’ve got a 12.3″ netbook (running Linux), and I don’t see any point in a variable zoom there either. Though I suppose it is 4:3 and hidpi.
Still, even at 768p you get a bespoke layout for your device, since this is literally the most common resolution still (seriously). The pinch-to-zoom on mobile is only useful for the very specific case of viewing unoptimized content (mostly desktop sites) in a comparatively smaller viewport. It’s not even useful on mobile if the website is optimized (sometimes for worse, but still).
It’s a nice to have, but hardly essential. But people are saying it prevents them from switching, so I am curious why.
