Search the Community
Showing results for tags 'dev'.
I’m a newbie to both Alfred development and GitHub version control. I built a new Alfred workflow called Sequential Strings Creator published on Github. I read some documents such as "Exporting and Sharing Workflows” but still confuse about the mechanism of shared release. That is, how should I release the next version so that other Alfred users can get it via the bundle ID? I plan to release the next version by the following steps: Clone the repo from Github remote to local Modify the files and fix the bugs Push the n
Here's a workflow that's useful for developers; it allows you to convert between timestamps and formatted datetime strings with ease. Simply type "df" followed by: "now", a UTC unix timestamp, or a formatted datetime string. This will present you with the parsed date in various formats ready to copy to your clipboard. Download
A significant problem in adding Alfred 3 features to my workflows is that Alfred-Workflow's update mechanism, which is based on GitHub releases and used by scores of workflows, has no way to tell if a workflow is Alfred 2 compatible or not. Either there's a release with a higher version number containing an .alfredworkflow file or there isn't. That's how GitHub releases work. Developers currently have 2 options to prevent their updated-for-Alfred-3 workflows trying to break themselves in Alfred 2: Start a new repo Mangle the release in some way that older library versions ignore it No.