Flow-Launcher / Flow.Launcher.PluginsManifest

Welcome to Flow Launcher's plugins repository This repository contains the information for community-made plugins used in Flow and how to make new submissions. Plugin list Looking for a list of currently available plugins in Flow? Visit here How to submit your plugin • Create a file named in the plugins directory. • Copy these items from your plugin project's file: • - • - • - • 3. Add , , and to the file. • It should look like this: • Optionally, a plugin can also have the property set, restricting it to only appear and be installable on versions of Flow Launcher that meet or exceed the specified version number. For example, setting ensures the plugin will not show up or be installable on any Flow Launcher version older than 2.0.0. • For , use a CDN provider for global accessibility. jsdelivr.com for example as shown above, works well with GitHub repositories. • It is a requirement to set up a GitHub Actions workflow for automated build and release. Follow the guide here and use this as an example. • It is a requirement that your plugin conforms with the Plugin Store policy. • Submit a pull request targeting the default branch. • The plugin will be available in Flow after the pull request is approved by the Flow Launcher Team. Flow downloads the manifest (plugins.json) file from various CDN providers, which means the availability of your new plugin depends on when these providers sync their updated files. This syncing process can take several days and sometimes up to a week across all providers. During this period, you may see intermittent updates for your plugin in the manifest, as the provider chosen for retrieval is selected randomly based on the fastest fetch speed. While the plugin has not yet appeared in the store, you and your users can manually install it using . How to remove your plugin • Remove the file for your plugin from the plugins directory. • Submit a pull request targeting the default branch. Note that the published manifest is regenerated by CI on a schedule (approximately every three hours) and then distributed via multiple CDN providers. As a result, your removed plugin may continue to appear in the plugin store or manifest for some time after your pull request has been merged, until all providers have refreshed their caches. Plugin updates Every three hours the *CI* in this repository will check for new updates from plugins and automatically update them to the latest version. So you do not need to manually submit a pull request after you make a new release. Plugin Store policy Plugins that facilitate or contain any of the following will not be allowed: • Malicious code • Piracy • Deceptive use • Inappropriate content • Illegal activities • Impersonation • Abuse • Fraud • Spam Plugin Store Users will be able to install your plugin via the store or type : Have a plugin enhancement request or issue? This repository does not track enhancement requests or issues for plugins, it is up to the plugin developers to maintain their own plugin. If you would like to contribute, submit a request or issue, please visit the plugin's repository via the 'UrlSourceCode' link or from , / on the plugin to go to the context menu and select 'Suggest an enhancement or submit an issue'.