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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
That's right, however GitLab is painfully unstable / less reliable compared to GitHub, IMHO.
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.