GitHub just launched “Actions”
I’m personally pretty into this sort of thing, but I haven’t taken a deep look into it.
What are your thoughts?
For further actions, you may consider blocking this person and/or reporting abuse
GitHub just launched “Actions”
I’m personally pretty into this sort of thing, but I haven’t taken a deep look into it.
What are your thoughts?
For further actions, you may consider blocking this person and/or reporting abuse
Antonio | CEO at Litlyx.com -
Gurigraphics -
rachelle palmer -
Syakir -
Top comments (20)
I think building in CI capabilities was something Gitlab got very, very right. GitHub relied on its marketplace to provide many of the services that Gitlab has built-in. I think they might be seeing users making the switch to GitLab, and reacting to that.
The visual way of setting up actions does look more intuitive than setting up GitLab Ci, though.
There are discussions here on implementing a visual editor for the
.gitlab.ci.yml: gitlab.com/gitlab-org/gitlab-ce/is.... With GitHub Actions, this will probably get prioritized.That's right, however GitLab is painfully unstable / less reliable compared to GitHub, IMHO.
Environmental variables for GH Pages is huge for my students -- I have a similar set up with Netlify right now that I'm super happy with for personal use, but they usually use pages and this will help a lot.
I have high hopes. I've fought with Jenkins, Travis CI, Circle CI, etc... throughout my career, I'm just kinda tired. Each thing has its own good stuff and bad stuff. I seriously just wanna run containers after hooks are fired. CircleCI and Azure DevOps come closest (sorry for the shameless Azure plug).
Circle is cool b/c it supports any GH org you own, but it uses remote docker daemons that come with some weird limitations, and that config file - all that YAML!
DevOps is cool because you can run docker compose things. And out of the box, each only run for commits and tags (iirc)
Not really sure if GH actions are good for CI - I'll probably keep existing stuff around (even if it's hacky) because why switch if I already did the work. But all the other stuff you could do! OMG all the other stuff.
Here's some top of my head (some stolen from here):
There's probably tons more too. Anyway, I like the flexibility that you can respond to any GH action, and that it's gonna be automatically on for any repo, and that you can do stuff in any language as long as you can do it in a Docker image
Just to mention an aspect I feel nobody else mentioned yet: GitHub totally takes over features, which used to be set up using the GitHub Marketplace – I do not want to know how people at Travis & Co. are feeling right now.
How many of the Apps in the GitHub Marketplace have been rendered useless this way?
Welcome to software development.
Think about vendors everytime AWS releases a new service :D
It seems like a Zapier way of doing DevOps on Github. But I'm happy with all new features they can add so as to not having a need to use any other of its competitors.
After years of pain with VSTF CI, I doubt MSFT had anything to do with this! :D
The newer cloud version is much less painful to implement.
GitHub Actions are awesome but I do not like they provide limited support for most open source projects that collaborate using forks. More on that in by post dev.to/derberg/github-actions-when...
Interested in an easy example of GitHub Actions build workflow? Please check my article about how we use GitHub Actions in our opensource project: BPMN Visualization
dev.to/aibcmars/simplifying-life-u...
take care
It looks pretty cool; I will love to use actions rather than writing my own integrations base on webhooks.
It remains me to Shopify Flow.
Perfect timing I'm developing a blog post on top of that.