7 ms·

Just a few years ago I was in love with Github and felt nothing could ever displace it. But as time went on, they just fell asleep at the wheel. I've been using

Just a few years ago I was in love with Github and felt nothing could ever displace it. But as time went on, they just fell asleep at the wheel. I've been using Gitlab for the last six months and there is no chance I would ever go back to being a paying customer of Github. I'm so glad to hear GitLab raised more money to keep going!

theunquietone 10y ago
So awesome to hear you're enjoying using GitLab! As always, let us know if you have any feature requests or see areas where we could improve. Cheers!
- alex_hitchins 10y ago
  I can only echo the comments here - switching to GL has been fantastic all round. I welcome the addition of other tools into the product. The closer the tools are the more effective they become.
  - jobvandervoort 10y ago
    > The closer the tools are the more effective they become. This has been our thought for a long time now and I'm happy to hear it from the community. See for instance our vision [0]. [0]: https://about.gitlab.com/direction/#vision https://about.gitlab.com/direction/#vision
lloeki 10y ago
Using both, I notice GitHub has moved, but GitLab has moved in precisely the direction we need internally, especially the latest release.
- jobvandervoort 10y ago
  Great to hear! What exactly did we do well? What can be better?
  - StavrosK 10y ago
    As a customer, I love the integrated CI and how easily I can now run tests for each commit and show pass/fail and coverage information right on the commit. We used to use Stash and Jenkins, but it was pretty hard to get the integration to work reliably. Another thing I love is the gitlab-runner, which lets me spin up a machine and have another server to run tests on. What I really don't love is how limited issues feel compared to JIRA. Namely, the following workflow is so hard it might as well be impossible: * Issue gets opened by a user/assigned to a developer. * Developer has a view that's only issues that they haven't worked on or that they're working on. * After the issue has been worked on, the developer can assign it back to QA. * QA retests and closes. This was very well served with JIRA's open -> in progress -> resolved -> closed pipeline, as well as with the views that could filter things like "show me issues assigned to me or nobody, that are not resolved or closed, ordered by priority". We tried to do something similar with labels and the board, but it's really inconvenient, because we can't filter for "show me issues that are NOT <something>". We used a "new" label instead, but the board doesn't know that "new" is the backlog and that that label should be removed when the issue moves out of the former. In general, we've been having problems with issues, although the milestone view is pretty fantastic.
    - jobvandervoort 10y ago
      Thanks for the awesome comment and details. > show me issues assigned to me or nobody, that are not resolved or closed, ordered by priority Right now, GitLab orders by priority out of the box on the board. You can filter for yourself or assigned to nobody. Not both, but we're working on improving the filters (including the option to do "NOT X OR Y". [0] > We used a "new" label instead, but the board doesn't know that "new" is the backlog and that that label should be removed when the issue moves out of the former. Just create a list with the 'new' label and you should be good, right? We're thinking about having different types of lists in Boards, such as 'Milestone boards' and 'Status boards'. Something like that could solve some of your requests as well. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21993 https://gitlab.com/gitlab-org/gitlab-ce/issues/21993
      - 10y ago
- FireBeyond 10y ago
  Agreed. While GitHub announces new features, mostly my reaction is "Huh, interesting", but will never use it. CI, Registry, Issues changes that GitLab is introducing is right on the money for what we want, need.

theunquietone 10y ago

So awesome to hear you're enjoying using GitLab! As always, let us know if you have any feature requests or see areas where we could improve. Cheers!

alex_hitchins 10y ago
I can only echo the comments here - switching to GL has been fantastic all round. I welcome the addition of other tools into the product. The closer the tools are the more effective they become.
- jobvandervoort 10y ago
  > The closer the tools are the more effective they become. This has been our thought for a long time now and I'm happy to hear it from the community. See for instance our vision [0]. [0]: https://about.gitlab.com/direction/#vision https://about.gitlab.com/direction/#vision

lloeki 10y ago

Using both, I notice GitHub has moved, but GitLab has moved in precisely the direction we need internally, especially the latest release.

jobvandervoort 10y ago
Great to hear! What exactly did we do well? What can be better?
- StavrosK 10y ago
  As a customer, I love the integrated CI and how easily I can now run tests for each commit and show pass/fail and coverage information right on the commit. We used to use Stash and Jenkins, but it was pretty hard to get the integration to work reliably. Another thing I love is the gitlab-runner, which lets me spin up a machine and have another server to run tests on. What I really don't love is how limited issues feel compared to JIRA. Namely, the following workflow is so hard it might as well be impossible: * Issue gets opened by a user/assigned to a developer. * Developer has a view that's only issues that they haven't worked on or that they're working on. * After the issue has been worked on, the developer can assign it back to QA. * QA retests and closes. This was very well served with JIRA's open -> in progress -> resolved -> closed pipeline, as well as with the views that could filter things like "show me issues assigned to me or nobody, that are not resolved or closed, ordered by priority". We tried to do something similar with labels and the board, but it's really inconvenient, because we can't filter for "show me issues that are NOT <something>". We used a "new" label instead, but the board doesn't know that "new" is the backlog and that that label should be removed when the issue moves out of the former. In general, we've been having problems with issues, although the milestone view is pretty fantastic.
  - jobvandervoort 10y ago
    Thanks for the awesome comment and details. > show me issues assigned to me or nobody, that are not resolved or closed, ordered by priority Right now, GitLab orders by priority out of the box on the board. You can filter for yourself or assigned to nobody. Not both, but we're working on improving the filters (including the option to do "NOT X OR Y". [0] > We used a "new" label instead, but the board doesn't know that "new" is the backlog and that that label should be removed when the issue moves out of the former. Just create a list with the 'new' label and you should be good, right? We're thinking about having different types of lists in Boards, such as 'Milestone boards' and 'Status boards'. Something like that could solve some of your requests as well. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21993 https://gitlab.com/gitlab-org/gitlab-ce/issues/21993
    - 10y ago
FireBeyond 10y ago
Agreed. While GitHub announces new features, mostly my reaction is "Huh, interesting", but will never use it. CI, Registry, Issues changes that GitLab is introducing is right on the money for what we want, need.