3 ms·
I've been on the beta for a while, and while it was understandably limited, I really enjoy it and have done a lot with it. I'm excited about the announcement be
by qubyte 7y ago
I've been on the beta for a while, and while it was understandably limited, I really enjoy it and have done a lot with it. I'm excited about the announcement because it appears that a lot more can be done now.
However, it's not clear what happens to existing actions and workflows. Do they just stop working? Can actions still be made from a dockerfile and entrypoint script?
- judge2020 7y agoSee - https://twitter.com/gimenete/status/1159521518403145728?s=20 https://twitter.com/gimenete/status/1159521518403145728?s=20 https://help.github.com/en/articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax https://help.github.com/en/articles/migrating-github-actions... Already used the "migrate-actions" binary on a few projects, and while I don't have the new version enabled (you'll get a notification when the repo is available for an upgrade), this is better in terms of simplicity since you don't have to manage action references or the "resolves" field (when you were manually editing the hcl). The only downgrade is that it doesn't look like you can run actions in parallel within the same "job"; so you can't have eg. "cd project1 -> npm i" and "cd project2 -> npm i" running at the same time and then have a third action that can use the output/filesytem of both of those commmands. Now the "job" will run one, wait for completion, then run the other, then you can have an action that uses the changes of those.
- qubyte 7y agoThanks for the links! I'll miss the old workflow and its syntax (allowing for parallelism), but I'm keeping an open mind.