love-actions/Love actions for macOS AppStore
macOS AppStore CI/CD for LÖVE based games
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Feb 21, 2023
- License
- None
Pinned Snippet
uses: love-actions/love-actions-macos-appstore@354da05aad5b1cb8c02549e9cd361c02015726be # v1.1.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| app-name | App display name Would be used in platform/xcode/macosx/love-macosx.plist | no | LÖVE for macOS |
| bundle-id | App bundle id Would be used in platform/xcode/love.xcodeproj/project.pbxproj | no | org.love2d.macOS |
| copyright | App copyright info Would be used in platform/xcode/macosx/love-macosx.plist | no | — |
| icon-path | Icon path Should be .icns format Would be used in platform/xcode/Images.xcassets/OS X AppIcon.appiconset | yes | ./icon.icns |
| love-ref | LÖVE git ref Could be commit hash, tags or branch name | no | fc3f5ee6209a0aab9a4d381ed5cd99110f9ff2f2 |
| love-patch | Git patch file path for the LÖVE repo The patch must start from `love-ref` You can use `git diff` to get the patch file | no | — |
| love-package | Love package Would be used to assemble the executable | no | ./game.love |
| libs-path | Path to the libs folder Would copy all contents to platform/xcode/ Top folder not included | no | — |
| extra-assets | List of file paths to be added to `Copy Bundle Resources` build phase Don't need global quotes, 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 |
| version-string | App version string Use 3 numbers seperated by dots Looks like 3.2.1 | no | 11.4 |
| output-folder | Packages output folder All packages would be placed here | no | ./build |
| apple-development-base64 | Apple Development certificate base64 content Would be used to sign the app | yes | — |
| apple-development-password | Apple Distribution certificate password Would be used to sign the app | yes | — |
| api-key | App Store Connect API key content Would be used to automaticly update profiles, app IDs and certificates | yes | — |
| api-key-id | App Store Connect API key ID Would be used to automaticly update profiles, app IDs and certificates | yes | — |
| api-issuer-id | App Store Connect API issuer ID Would be used to automaticly update profiles, app IDs and certificates | yes | — |
| team-id | Developer team id Would be used to sign the package | yes | — |
| apple-id | App Apple ID Would be used to upload the package | yes | — |
| external-test | Deliver the package to the Testflight external groups | no | false |
| store-release | Deliver the package to the App Store release | no | false |
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.pkg |