mperezi Posted March 23, 2020 Share Posted March 23, 2020 Hey guys, I've just created this handy GitHub Action to build .alfredworkflow files for your releases: https://github.com/marketplace/actions/build-an-alfred-workflow And this is the repo where I use the action: https://github.com/mperezi/alfred-yaml Hope you find it useful! deanishe 1 Link to comment
vitor Posted March 23, 2020 Share Posted March 23, 2020 Seems like you’re basically compressing the Workflow into a zip, which will not work correctly and can expose sensitive information in the output, such as API keys or location. You need to first empty any variablesdontexport keys from the plist. Link to comment
deanishe Posted March 23, 2020 Share Posted March 23, 2020 (edited) Very nice idea. 35 minutes ago, vitor said: You need to first empty any variablesdontexport keys from the plist. Agree that such variables must be stripped (because that's the proper way to build a workflow), but any sensitive data needs stripping before you commit the source. I use git hooks to prevent me committing any sensitive variables. More generally, I think it's not a good idea to require info.plist and icon.png to be in the repo root. They should be in workflow_dir anyway, otherwise it isn't a valid workflow. I don't know how you develop your workflows, @mperezi, but it's common to symlink src to Alfred's workflow directory for development. The workflow itself lives in there, so you don't clutter it with things like your editor config files or .git directory. Edited March 23, 2020 by deanishe Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now