Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab 10.6 released with CI/CD for GitHub

about.gitlab.com

Post reply on HN
Print view View original

61–70 of 107 posts

Re: GitLab 10.6 released with CI/CD for GitHub

#61

Post by jobvandervoort »

gtirloni wrote: post #36
andrewstuart2 wrote: post #28

Earlier quoted context omitted.

It's open source. I'm sure they wouldn't turn down a PR if you submitted one. I've poked around the codebase a few times; it's not too hard to contribute, despite my lack of experience with ruby.

It's open core , not open source. I'm pretty sure they would have a lot of incentives to turn it down.

We don't have a lot of incentives to turn down contributions. Quite the opposite.

We not only encourage this, we actively help people contributing to GitLab. It's humbling to be a steward to an open source project and something we don't take lightly [0].

And to be blunt, for an organisation as ours, with very ambitious goals, and highly demanding users, having someone else than us contribute something that makes the product better is the best possible deal we could do. We can compensate for the 'lost' value in our enterprise product by spending that time on other things that are maybe more interesting for our paying customers.

[0]: https://about.gitlab.com/stewardship/

Re: GitLab 10.6 released with CI/CD for GitHub

#64

Post by chinhodado »

0x0 wrote: post #25
chinhodado wrote: post #24

I hate it that Gitlab is focusing too much on all these project-management features, while neglecting the basic code review features such as commenting on a block of code, or making a review session instead of creating individual comments, or the ability to blame previous revisions of a file

At least you can blame previous revisions of a file? Using an URL like gitlab.com/username/project/blame/COMMITHASH_OR_TAG/path/to/file

You can, but you need to copy-paste the hash to the URL manually, which is not exactly good UX.

Re: GitLab 10.6 released with CI/CD for GitHub

#65

Post by williamchia »

eslaught wrote: post #60
Snappy wrote: post #49

Earlier quoted context omitted.

FWIW, if you created the connection between GitLab and GitHub for your project before 10.6, you'll have to remove the connection and then re-add it to get the push-based mirroring to happen. Otherwise, yes, it will still poll.

How do you do this?

It seems like you should be able to do this, but there may need to be an update to work with already-mirrored repos since the feature was designed to have a flow that expects a new project to be created.

I've logged an issue to track down the process: https://gitlab.com/gitlab-org/gitlab-ce/issues/44552

Re: GitLab 10.6 released with CI/CD for GitHub

#66

Post by victorwu »

chinhodado wrote: post #58
victorwu wrote: post #43

Earlier quoted context omitted.

Here's an example of a blame on a previous commit of a file. https://gitlab.com/gitlab-org/gitlab-ce/blame/57ce7c655cc58e... Did you have some particular feature request beyond this view?

The use case is to be able to repeatedly blame on the previous revision of the change that was made to a line. This is especially useful when you're dealing with diffs resulted from code formatting, whitespace changes, etc. in a file and you want to see what is the "original" commit that the change was made. This has been available on GitHub for a while now (see https://help.github.com/articles/tracing-changes-in-a-f…

Thank you for the explanation. I've created an issue. Feel free to continue the discussion there.

https://gitlab.com/gitlab-org/gitlab-ce/issues/44553

Re: GitLab 10.6 released with CI/CD for GitHub

#67

Post by dogweather »

ninkendo wrote: post #2

Since "X adds support for Y" is nearly always ambiguous and confusing: It looks like GitLab's CI/CD system can now be pointed at GitHub repositories. So that means you can point your GitLab CI system at a GitHub repo and get build/test/deployment of your code, probably integrated with PR checks and so forth.

So GitLab's CI/CD is now modularized and theoretically can be used in place of Circle CI or similar?

Re: GitLab 10.6 released with CI/CD for GitHub

#68

Post by dogweather »

chinhodado wrote: post #24

I hate it that Gitlab is focusing too much on all these project-management features, while neglecting the basic code review features such as commenting on a block of code, or making a review session instead of creating individual comments, or the ability to blame previous revisions of a file

Or basic modern web UX. Like using a wide screen effectively.

Re: GitLab 10.6 released with CI/CD for GitHub

#69

Post by tmuir »

vortico wrote: post #9
ninkendo wrote: post #2

Since "X adds support for Y" is nearly always ambiguous and confusing: It looks like GitLab's CI/CD system can now be pointed at GitHub repositories. So that means you can point your GitLab CI system at a GitHub repo and get build/test/deployment of your code, probably integrated with PR checks and so forth.

The original title was "GitLab adds support for GitHub". Now that GitLab supports GitHub, I'll go to GitLab for all my support questions about using GitHub!

Pssh. Gitlab was obviously just tallying the individual sentiments of whether the users were generally in favor of Github continuing to exist as an organization. How could you have missed this?

Re: GitLab 10.6 released with CI/CD for GitHub

#70

Post by tmuir »

victorwu wrote: post #66
chinhodado wrote: post #58

Earlier quoted context omitted.

The use case is to be able to repeatedly blame on the previous revision of the change that was made to a line. This is especially useful when you're dealing with diffs resulted from code formatting, whitespace changes, etc. in a file and you want to see what is the "original" commit that the change was made. This has been available on GitHub for a while now (see https://help.github.com/articles/tracing-changes-in-a-f…

Thank you for the explanation. I've created an issue. Feel free to continue the discussion there. https://gitlab.com/gitlab-org/gitlab-ce/issues/44553

Does this mean that gitlab doesn't generally employ people to simply learn their competitors products, to keep informed of their offerings?
Post reply on HN