love-actions/Love actions for Windows

Windows CI/CD for LÖVE based games

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Maintainedlast commit Oct 8, 2025
License: None

Pinned Snippet

workflow.ymlSHA-pinned

uses: love-actions/love-actions-windows@36cae8246a339241633135d1e74346008d32d20b # v1.1.3

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
love-ref	Love release ref Could only be release tags like '11.5'	no	11.5
love-package	Love package Would be used to assemble the executable	no	./game.love
icon-path	Path to the icon Would be used in building exe If not provided, the product will not have an icon	no	—
rc-path	Path to the .rc file will be used to set the metadata of the exe If it is not provided, the compiled exe file will not have any metadata defined by the .rc file	no	—
extra-assets-x86	List of folder & file paths to be added to x86 product folder No global quotation marks, separated by spaces Looks like: ./assets/ ./logics/ ./main.lua ./config.lua	no	—
extra-assets-x64	List of folder & file paths to be added to x64 product folder No global quotation marks, separated by spaces Looks like: ./assets/ ./logics/ ./main.lua ./config.lua	no	—
product-name	Base name of the package Would be used to rename products	no	love_app
app-id	The application identifier for the installer If not provided, the installer will not be build	no	—
project-website	The project's homepage url	no	—
installer-languages	List of languages supported by the installer No global quotation marks, separated by spaces	no	—
output-folder	Packages output folder All packages would be placed here	no	./build
love-actions-folder	Path to the love-actions-windows folder Would be used to run all the action steps	no	./love-actions-windows

Outputs

name	description
package-paths	Paths to the built packages in a bash list Would be paths relative to repository root, separated by spaces Looks like: ./build/game.apk ./build/game.abb