Earlier quoted context omitted.
github has self-hosting. It is a little pricey but that is not a product differentiator.
Price isn't a product differentiator?
[deleted]
Announcing new tools, forums, and features
161–170 of 282 posts
Re: Announcing new tools, forums, and features
#162If anyone from Github reads this, a) this looks great, b) add project templates please, so we don't have to recreate the same columns every time. Thanks. <3
d) create issue templates also, i have to currently cut and paste the same markdown into every issue
e) create user-level permissions - i work on a team where everyone would use this, but currently not everyone can have access to the code base so we have to say in trello until you can allow me the ability to turn off code access to "non-engineers"
Re: Announcing new tools, forums, and features
#163I'd really like it if the Pull Requests page would denote which PRs I've already approved. That is one thing I really liked from Bitbucket, it makes it easy to skip over what I've already approved. It would become slightly more complex though, because then you'd probably want to see something for PRs you've approved but had subsequent changes on.
Great feedback point here - I've passed it along to our Engineering team.
Thank you! Can I make one more request? I'd love to be able to see merge conflicts from the diff page (also like BB does).
Knowing the conflict is just db/schema version instead of something more problematic-- that is especially handy when used in conjunction with various target branches.
i.e. I know branch is about to be merged before right before gets merged. Then, I can know what I'm going to have to fix quickly without having to go back to terminal, fetch , merge , just to find the conflicts. Yes, I have to do that with master after it's merged anyways, but I find it great to see quickly and at a glance beforehand.
Re: Announcing new tools, forums, and features
#164Earlier quoted context omitted.
> Open source* The Enterprise edition features[1] are closed source, and these aren't strictly "enterprise-y" features like SAML authentication. It includes plenty of "basic" workflow features found on GitHub: - Rebase merge requests before merge - Use fast-forward merges when possible - Create templates for issues and merge requests - Display merge request status for builds on Jenkins CI [1] https://about.gitlab.com…
To make sure there is no confusion we now refer to ourselves as open core https://about.gitlab.com/about/#stewardship I want to echo here what I said in https://news.ycombinator.com/item?id=12501271 "If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found…
> 1. Can you rebase in the GitHub interface?
> 2. Does GitHub have an option to fast forward merges?
So is Gitlab's aim to just play catchup to Github?
Re: Announcing new tools, forums, and features
#165Earlier quoted context omitted.
github has self-hosting. It is a little pricey but that is not a product differentiator.
No-one said it was. But the answer of self-hosting is a perfectly valid answer for "Why the love for GitLab?" when one = $0 in licensing, and the other = > $2,500/year in licensing.
> No-one said it was.
That is literally what the comment I replied to said. That "self hosting" was a reason to root for gitlab.
Re: Announcing new tools, forums, and features
#166Earlier quoted context omitted.
I think it was more the open letter to Github, which motivated both Github and GitLab (seen as an opportunity to compete). GitLab's roadmap yesterday surely didn't motivate or spawn the "New GitHub Universe," and I wouldn't think that Github is very nervous about GitLab currently due to it's massive lead in the market. Maybe this new round of funding made some of the folks at Github look over at Gitlab, but I doubt t…
> massive lead in the market Ehh... dominance among open source projects, and Hacker News and Reddit thread cool points, is one thing. But in boring old terms of actually making money, how IS GitHub doing? "Enterprise" is practically a swear word here, but that's where the meaningful paying customers are. From my anecdotal experience, Atlassian absolutely dwarfs GitHub in the enterprise world... and that's just the e…
> "Enterprise" is practically a swear word here, but that's where the meaningful paying customers are. From my anecdotal experience, Atlassian absolutely dwarfs GitHub in the enterprise world... and that's just the enterprises that are willing to host code in the cloud to begin with.
I was recently at an F1000 company and we did self-hosted GitHub Enterprise. While many services were duplicated across departments, there were a variety of other commercial VCS setups, and our GH was not highly available… there was a ton of buy-in to GitHub Enterprise. And, yeah, we did JIRA and Confluence (and SharePoint…).
I'm doing a gig for a F100 company now and, well, we've got GitLab. I dunno if I'm just more used to GitHub or if I actually prefer it to GitLab.
Re: Announcing new tools, forums, and features
#167Hmm.. So was there a workflow where I could say "I'd like for this not to be pushed until I've approved it", even if the patch is assigned to be reviewed by someone else? Of course, I could just comment with that on the issue, but it would be nicer if the issue would pop up somehow after the other reviewer has reviewed it, and it would be obvious to everyone that it's waiting for my approval.
Re: Announcing new tools, forums, and features
#168Earlier quoted context omitted.
To make sure there is no confusion we now refer to ourselves as open core https://about.gitlab.com/about/#stewardship I want to echo here what I said in https://news.ycombinator.com/item?id=12501271 "If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found…
> 1. Can you rebase in the GitHub interface? > 2. Does GitHub have an option to fast forward merges? So is Gitlab's aim to just play catchup to Github?
We already have these features, we just opted to make them EE/.com only since we think they are more relevant for organizations that have more than 100 potential users.
We have a broader scope than GitHub, see our announcement broadcasted on Tuesday for more information and a demo https://about.gitlab.com/2016/09/14/gitlab-live-event-recap/
Re: Announcing new tools, forums, and features
#169Earlier quoted context omitted.
We're happy that you're happy. :) Keep the feedback coming; we're listening!
I'm liking the recent design changes, however, I don't like the new implementation of contrib. activity... information overload!
Ah, noted - so you'd like to have some customization on what you choose to show on your profile?
Re: Announcing new tools, forums, and features
#170Earlier quoted context omitted.
Great feedback point here - I've passed it along to our Engineering team.
Thank you! Can I make one more request? I'd love to be able to see merge conflicts from the diff page (also like BB does). Knowing the conflict is just db/schema version instead of something more problematic-- that is especially handy when used in conjunction with various target branches. i.e. I know branch is about to be merged before right before gets merged. Then, I can know what I'm going to have to fix quickly w…
Certainly - thanks for that! I've included it here.
We're aiming to monitor this board as much as possible, but if there other feature asks that come up, feel free to connect with our Support team - they're also available to take your feature asks and report them to our Engineering team.