Were you #movingtogitlab before it was the thing to do? We want to acknowledge our community for supporting us from the beginning – find out how you can get your hands on a limited edition GitLab Originals T-shirt.

Data analytics startup Cognitive Logic helps companies store, share, and examine consumer information without compromising security. I sat down with engineer Johan Brandhorst to learn more about his team, their work, and how GitLab helps.

Three of our offerings in particular drove Cognitive Logic's decision to switch to GitLab:

Willem de Groot published a list of web stores that contain malware. He first hosted this list on GitHub but it was deleted. Then he hosted it on GitLab where it was also deleted. The reason we gave him for the deletion was "GitLab views the exposure...

With the release of GitLab 8.9, GitLab now supports the FIDO Universal 2nd Factor (U2F) protocol for user authentication with the added layer of hardware security from YubiKey. We're excited to expand our authentication capabilities to include U2F devices. U2F changes the game for online authentication because it uses public key cryptography and has built-in support to prevent phishing. This higher level of authentication enables developers to maintain the security of their servers, code, sites, and more from a single source.

After GitLab 8.5 was released, we looked for a way to improve the current user interface for both new and experienced users. One of our biggest concerns was that it was easy to get lost in the navigation hierarchy with what we currently had. New users were quite confused by how the left sidebar constantly changes with new links to different pages. At the same time, as an experienced user, I was annoyed by the old navigation too.

So Andriy (our UX designer) and I decided to do something about it. It's been almost 4 months now that we are working on it, and in this post I will guide you through our journey. Feedback is welcome!

We are very excited to announce that we recently welcomed our 1,000th contributor! And, the list keeps growing. Since we released the first open source version of GitLab in 2011 our community of contributors has been absolutely essential to growing...

Today GitHub announced pricing changes to all of their paid plans on GitHub.com. With these changes, paid plans on GitHub.com will now include unlimited private repositories. At GitLab, we were not surprised to hear about these pricing changes. We believe they are inline with how pricing will move in the future. At GitLab, we think per-user pricing is the best pricing model because it is more predictable, less restrictive on code, and aligned with value the organization gets.

May is a very busy and exciting events month for our team! Since we are a remote first company, we rarely get to meet in person, but this month the whole team is meeting in Austin, TX for OSCON. The last time we met was in October and since then the team has grown significantly. We get to meet each other face to face for the first time and hopefully get to see some of you throughout the month as well.

The following are some upcoming events and where you can meet our team.

If you'll be coming to these events, please say hello in the comments or ping us (@gitlab) or the attendees via Twitter. We'd love to meet you.

GitLab 8.7 improves Issues, makes diffs easier to work with, brings better commenting, allows you to push to remote repositories, and more. In our latest webcast, we looked at the highlights from this release.

Our Backend Lead, Douwe Maan, gave us a live demo of the latest features in GitLab 8.7. He walked us through a common user scenario to demostrate how these new features will benefit our users.

Today, we are excited to announce our partnership with DigitalOcean, the world’s simplest cloud infrastructure provider. Together, GitLab and DigitalOcean want to help developers eliminate the scaling challenges that come with Continuous Integration (CI), such as speed, security, and cost. To help alleviate these challenges, GitLab partnered with DigitalOcean to provide free Runners to all projects on GitLab.com as well as discount codes for GitLab Community Edition and Enterprise Edition users.

Our team is growing! Since we're remote only we have no real headquarters where you can meet the GitLab team. The great thing about being remote is we've got team members all across the globe, active in their own communities and giving talks or presentations. In this post we give you a list of some upcoming events and where you can meet our team.

If you'll be coming to these events, please say hello in the comments. We'd love to meet you.

Since GitLab 8.0, GitLab CI is an integrated part of GitLab. This web application manages projects/builds and provides a nice user interface.

In our next webcast on April 14th, we'll take a look using continuous integration in GitLab. Join the GitLab CI team to ask questions and find out how to get the most out of the built-in continuous integration with GitLab.

Funding an open source project and maintaining an organization to sustain that project is a challenge. We've chosen an open-core model which means we have an MIT licensed open core, GitLab Community Edition (CE), and an extended GitLab Enterprise Edition (EE) for which we sell a license key to use. In this post we will look at the Fair Source license.

Today we are announcing an update to pricing for GitLab Enterprise Edition. We have replaced the three subscription plans (Basic, Standard, and Plus) with one simplified plan. Please visit our Pricing page for more information, or read on for a summary.

In our latest webcast, we highlighted a typical daily workflow when using GitLab. We looked at features in GitLab which emphasize conversation, collaborating early, improving discoverability, and keeping your momentum going.

Job showed how he starts his day, checking his todo list, providing feedback on issues, line-by-line code review, and getting to work on his own commits. This demo is based on GitLab Flow which is lightweight and scales easily for even large teams. Watch the recording below.

In our latest webcast, we highlighted the new features in GitLab 8.5. This was a really feature-packed release.

Job van der Voort gave a step-by-step tutorial of a workflow with GitLab. This highlighted some of the new features in the context of collaboration. If you're brand new to GitLab this is a quick introduction to how it works.

We're delighted to announce that GitLab Community Edition has been accepted as a project for the upcoming Rails Girls Summer of Code. Students will be working on improving GitLab not only for GitLab.com but for all GitLab users, be it individuals or large corporations such as SpaceX, NASA, CERN, and IBM. A regular release interval means changes made by students will be available quickly, instead of waiting in a queue for months.

Note: An earlier version of this post opened this sponsorship to anyone outside of New York and the Bay Area but we've removed that restriction.

Improving diversity in tech has become an important issue in the last few years. Organizations and events tailored specifically for underrepresented groups are getting increasingly popular and it has been amazing to watch the progress in the tech world. While we aren’t completely on equal footing yet, there are many people making great strides. I’ve attended and helped organize many of these events and would like to help broaden that reach to beyond the major tech centers of the U.S.

On January 22nd we'll release our 50th monthly release. We want to take this time to celebrate this milestone with GitLab users. You can join us for a webcast the following week, Thursday, Jan 28th, 5pm (17:00) UTC; 12pm EST; 9am PS.

Happy new year, it's a fresh start! Are you making any resolutions? Any plans? Wouldn't it be great if you could see into the future? With GitLab, you can. Well, okay, you can see into the future of development at GitLab, if nothing else. The plans and progress of feature proposals are developed in the open at GitLab. In this post we'll look at how you can find out about the direction of the project.

Today we are announcing two big changes to the GitHost platform and to its plans and pricing. The changes are intended to offer a better product with greater features and easier to use configuration options, to better reflect the storage and memory needs organizations have for a hosted instance of GitLab, and to make it sustainable for us to offer a service like GitHost. Please read on for all the details.

Companies and developers who use Ruby depend on a lot of infrastructure to get their work done. GitLab provides a solution for hosting code and collaborating on that code, but shipping code and using code shipped by others also relies on Bundler, RubyGems, and the RubyGems.org servers. For many years, all of that Ruby infrastructure has been maintained entirely by volunteers, in their spare time. That worked well when the Ruby community was small, but today volunteer work just isn’t enough to keep everything working.

As the use of Git and GitLab becomes increasingly popular in the development world, we’re seeing people in other industries use GitLab as well. Versioning video files, images, and even microchip designs, teams need to be able to work collaboratively to version any type of large file efficiently and reliably.

In order to better serve our community with a need to version large files, support for Git Large File Storage (LFS) is now included in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition. Now game developers, graphic designers, mobile app developers, and anyone else building software requiring large files can use GitLab to version all of their assets.

GitLab and Tower, the popular Git client, have more in common than just "Git". They share the same goal: to make working with code easier. And just recently, with the release of Tower 2.3, they work together more seamlessly than ever.

You would think that cloning a remote repository was a simple process. And yet it can be quite a drag: You have to find the repository you want to clone, get hold of its URL, remember your authentication credentials (and method!) and fumble them onto the keyboard…

Solving such minor and major annoyances around Git has always been our motivation for creating Tower - a GUI client for Git that's now used by over 50,000 customers like Apple, Google, and Twitter.

Since our recent update to version 2.3, Tower makes working with GitLab even easier. You can access your repositories right from within Tower and clone them with just a single click:

Long gone are the days of wrestling with usernames, passwords, tokens, or URLs. Even creating new repositories in your account can be done via Tower. Cloning and managing repositories has become quite a bit easier.

Let's look at some other pain points that developers face day after day.

Today we're excited to announce the Pivotal Cloud Foundry tile for GitLab Enterprise Edition. With this partnership, developers will be able to easily deploy GitLab as a pre-configured appliance using Ops Manager (BOSH) for Pivotal Cloud Foundry.

Taking a trip down memory lane:

Once considered a radical upstart, open source has moved from disruption to default. Its methods and culture commoditized the technologies that drove the Internet revolution and transformed the practice of software development.

Since 1999, O’Reilly Media has organized OSCON, an annual convention for the discussion of free and open source software.

OSCON is where all of the pieces come together: developers, innovators, business people, and investors. At OSCON, you'll find everything open source: languages, communities, best practices, products and services. Rather than focus on a single language or aspect, such as cloud computing, OSCON allows you to learn about and practice the entire range of open source technologies.

GitLab will be sponsoring OSCON in Amsterdam from October 26th to October 28th, 2015. Would you like to join us?

Today Perforce launched Helix GitSwarm built on top of GitLab. GitSwarm combines Perforce and GitLab to enable easy project and team management while allowing developers to collaboratively code using their preferred version control system, Git.

Today we are proud to announce our $4 million Series A funding from Khosla Ventures. This follows our seed round in July.

GitLab will leverage the new funding to accelerate growth and scale its global operations including development, marketing, and sales. Additionally, GitLab announced the upcoming release of GitLab 8.0, which is scheduled for release on September 22. GitLab 8.0 will include 50 percent less disk usage, faster merging, Continuous Integration (CI) built into GitLab itself, improved interface and navigation, and "Reply by email" functionality that allows users to quickly comment on an issue or merge request from their mobile devices.

More than 100,000 companies and organizations currently use GitLab on-premises including NASA, CERN, Alibaba, SpaceX, O’Reilly, IBM, and Expedia. These organizations and many individual contributors hack on, contribute to, and help GitLab become better every single day.

It is our goal to become the default solution for anyone building software and working together. The excitement and passion of our community has convinced us that open-source is the way forward. We want to accelerate our growth and expand operations so we can reach more people and build an even better GitLab.

As the GitLab community keeps growing, we believe it's vital to integrate with other services and support the open source movement. We would like to facilitate researchers' efforts by integrating GitLab with the Open Science Framework (OSF). We will jointly sponsor a USD 8,000 - 10,000 grant through the Center for Open Science (COS) for the developer (or team of developers) who helps us integrate GitLab with OSF.

This morning GitLab.com was offline for one hour while we were investigating what seemed to be a filesystem corruption issue. With this blog post we want to tell you more about what was going on and what we discovered.

We're very excited to announce that we'll ship GitLab Mattermost, an open source, on-premises messaging app (like Slack) along with GitLab. GitLab Mattermost will first be included with the Omnibus packages of GitLab 7.14 (due August 22nd). We think GitLab Mattermost will be a great addition for GitLab users that need all software on-premises.

Update

Original article

At GitLab we would love to be compatible with Git Large File Support (LFS). We plan to base our implementation on a reference implementation that is currently not in a production ready state. But we hope that over time we can get to production level support. What follows is some background how and why we are taking this path instead of reusing an existing solution.

GitLab started as a on-premises software where Dmitriy could put his repositories. Open-source; built by and for developers, our community grew quickly to hundreds of contributors world-wide.

Today, over a hundred thousands organizations are using GitLab to build software that puts people in space (NASA, SpaceX), helps discover new particles (CERN) and move computing forward (IBM, Qualcomm), among many others. These organizations and many individual contributors hack on, contribute and help GitLab become better every single day.

It is our goal to become the default solution for anyone building software and working together. The excitement and passion of our community has convinced us that open-source is the way forward. We want to accelerate our growth and expand operations so we can reach more people and build an even better GitLab.

In the effort to reach our goal, we are excited to announce that we have raised $1.5M in seed funding led by Khosla Ventures, 500 Startups, Crunchfund, Sound Ventures (Ashton Kutcher), and Liquid 2 Ventures (Joe Montana).

As an organization, GitLab is fully distributed where employees are free to work from wherever they feel most productive. Likewise, our customers hail from all corners of the globe but mostly North America. So today we will begin operating as GitLab, Inc.

With less than a week until GitLab 7.12, we've got a nice preview for you today: Merge Request Approvals in GitLab EE.

Usually you accept a merge request the moment it is ready and reviewed. But in some cases you want to make sure that every merge request is reviewed and signed off by several people before merging it. With GitLab Enterprise Edition 7.12, you can enforce such a workflow that requires multiple reviewers with the new Merge Request Approval feature.

Today we are announcing two changes to GitLab Enterprise Edition subscription pricing. The changes are intended to better reflect the value of each offering and ensure our subscription options cater to the needs of different organizations.

In short, our basic subscription is now $19,10 more expensive, but in 10-user packs. Our Plus subscription is now $100 more affordable. Standard and terms remain unchanged.

Although the preferred way to install GitLab is to use our omnibus packages, you can also install GitLab Community Edition or Enterprise Edition 'from source'. If you used this installation method, and if you compiled Git from source in the process then please check whether your Git version defends against Git vulnerability CVE-2014-9390. This issue does not apply to our Omnibus packages (DEB or RPM).

A recently announced Logjam vulnerability allows an attacker to do a man-in-the-middle attack, allowing them to downgrade a TLS connection to 512-bit DH parameters. More details on what that is and means can be found on openssl blog.

In early March of this year, it was announced that GitLab would acquire Gitorious and shut down gitorious.org by 1 June, 2015. Reactions from the community were mixed, and understandably so: while GitLab itself is a formidable alternative to wholly proprietary services, its acquisition of Gitorious strikes a chord with the free software community that gathered around Gitorious in the name of software freedom.

In case you didn't know yet: Every single GitLab installation ships with a powerful continuous integration tool: GitLab CI. Read how to enable it in 2 minutes. With GitLab CI you can run tests of your projects and triggers builds and deployments easily, as it integrates deeply with GitLab.

Up until now, to set up the build / deploy commands you had to go into GitLab CI and edit the scripts in a form. This made it very low-threshold to set up, but it felt lacking.

We're glad to tell you we'll get a better solution built on the principles and libraries of Travis CI: .gitlab-ci.yml.

Not long time ago I built and wrote about the alternative CI runner written in Go. The single binary that can be easily run on any server with support for all latest technologies, including Docker. If you are interested here's blog post about it: Unofficial GitLab Runner. With great help of the community involved in testing today the runner becomes the official one, making the old one written in Ruby deprecated.

Today GitLab acquires GitHost, a provider of single tenant 'managed cloud' GitLab instances. GitHost is a great solution for people wanting to have a dedicated GitLab instance on their own domain name without the operational responsibility. You can also use it to run GitLab CI or to launch runners for GitLab CI.

The best thing of an open source project, GitLab in particular, is the community. Not only does the community provide us with much needed feedback, but in our case, they often send us awesome new features themselves that are in high demand.

This gives us an edge versus Bitbucket, which has a long list of requested features, but doesn't seem to be responsive to their users.

To convince some of you to move from Bitbucket to GitLab.com, we've compiled a list of our advantages versus them. We'd love to hear what you think in the comments.

We want to congratulate GitHub on launching git-lfs today, their method for storing large files. Their command line client looks easy to use since you can use existing git commands, a very nice innovation.

Today Google announced that its Google Code project hosting service will be closing in about 10 months. Back in 2006 when Google Code was first introduced, options for project hosting were pretty limited. Now there are many more options to choose from.

Last week, GitLab announced its acquisition of Gitorious, creating a strong player for open source software to create, review and deploy code. In this interview with OpenSource.com GitLab co-founder and CEO, Sytse Sijbrandij, talks about what led to...

We're happy to announce that GitLab now has Amazon Web Services Machines Images (AMIs) available for GitLab CE. These are simple AMIs, that only require a single command to bootstrap your GitLab instance on AWS.

Y Combinator, a Silicon Valley based seed fund, provides mentorship, advice and connections to a meticulously selected group of startups in two batches each year. Previous startups that went to the program include Dropbox, AirBnB, Stripe and Reddit. Y Combinator has also funded some of the best tools for developer community - including Heroku, CoreOS and Docker. Being selected by Y Combinator is a fantastic opportunity to learn from successful startup founders and leverage the experience of Y Combinators’ extensive network.

As reported by the Next Web GitLab and Gitorious announce today they are joining forces in an effort to strengthen the development of GitLab’s open source Git management application and provide Gitorious customers with an enhanced user experience.

Since 2008, Gitorious has been one of the leading providers for open source hosting and on-premises enterprise Git management around the globe. Gitorious was the first widely used open source Git management application.

“We believe that, in the long term, coming together under one umbrella with a common goal will benefit everyone, so we are getting that process started today” says GitLab CEO, Sytse Sijbrandij.

The biggest limitation of git compared to some older centralized version control systems has been the maximum size of the repositories. The general recommendation is to not have git repositories larger than 1GB to preserve performance. Although GitLab has no limit (some repositories in GitLab are over 50GB!) we subscribe to the advice to keep repositories as small as you can.

Not being able to version control large binaries is a big problem for many larger organizations. Video, photo's, audio, compiled binaries and many other types of files are too large. As a workaround, people keep artwork-in-progress in a Dropbox folder and only check in the final result. This results in using outdated files, not having a complete history and the risk of losing work.

In GitLab 7.8 Enterprise Edition this problem is solved by integrating the awesome git-annex. Git-annex allows managing large binaries with git, without checking the contents into git. You check in only a symlink that contains the SHA-1 of the large binary. If you need the large binary you can sync it from the GitLab server over rsync, a very fast file copying tool.

Are you working on a serious software project? You probably have an extensive test suite that takes a while to run. Why not run only the directly related unit tests locally and have your CI server take care of the rest 3x faster than you could? This way you can start with the next feature while your feature branch is being tested.

Having the tests run 3x faster on the CI server requires adding multiple workers to execute the tests in parallel. So far this has been very expensive, but with GitLab CI it is affordable for everyone.

Yesterday the Ghost vulnerability in glibc was announced. A bug in a networking function in the version of the C standard library found on many Linux systems can potentially lead to remote code execution. There is no indication at this time that this bug can be exploited against GitLab but it is nevertheless recommendable to install the latest updates from your OS vendor. In this post we will tell you how we did this at GitLab B.V.

Want to host your public and private repositories somewhere for free? You can on GitLab.com, where we have been hosting a single instance of GitLab for a while now. Almost 20,000 people make active use of this to host their repositories. The 100,000+ repositories that these people use are served by a single server.

A critical Git security vulnerability was announced yesterday, that affects all versions of the official Git client. Since this is a client-side only vulnerability, GitLab.com, GitLab Community Edition and GitLab Enterprise Edition are not directly...

Three days ago, Gollum, the git-powered wiki that is used in GitLab disclosed a vulnerability that makes it possible to execute code on the server that Gollum is running. Someone could exploit this to bring down your server or access your data. GitLab is not vulnerable for this, here's why:

Starting October 13th Patricio will join the GitLab team as a Junior Service Engineer. Together with Job and Jacob they will be providing support to our customers, support the GitLab open source community and help grow GitLab.

Today it is three years ago that the first commit to GitLab was made. We strongly believe that the best years are still ahead and want to share our vision for GitLab.

We do this as the sole shareholders of GitLab B.V., Dmitriy Zaporozhets and Sytse Sijbrandij. GitLab B.V. is the commercial entity that releases GitLab, offers paid services and runs GitLab.com.

Before describing our vision we want to share how GitLab started. GitLab was started in 2011 by Dmitriy Zaporozhets and Valeriy Sizov. They started it because they had a need for a tool that they could use locally in freedom. Living in the Ukraine they had limited resources, to this day Dmitriy has no running water at his house. But instead of leaving the Ukraine they want to build a future there. And after creating GitLab Dmitriy started to work two jobs. During the day working for his consultancy and when he got home improving GitLab. The problem was that the second job didn't pay anything, but Dmitriy didn't care.

Starting today, I'm joining the GitLab team as a software developer where I'll be working on GitLab CE and EE. I started the GitLab project together with Dmitriy 3 years ago. Today, we are together again :) I like Ruby, UNIX, git and other cool technologies...

Working from the San Francisco Bay Area, Haydn Mackay joins Gitlab.com as Major Accounts Manager to serve as a point of contact for existing and prospective customers, and help build our growing community.

Background

GitLab is a massive open source project with over 600 contributors, all working together to create an amazing platform to collaborate on code. Every month on the 22nd, a new version of GitLab is released, and every month new features are added. To make you aware of the power of GitLab, we walk through some of its features in these blog posts.

Background

GitLab.com now runs GitLab Enterprise Edition (EE). GitLab.com is our free SaaS offering allowing you to use GitLab with private repositories and unlimited collaborators. You now get to use the most fully featured GitLab edition on GitLab.com.

Today we rename our Software as a Service (SaaS) offering from GitLab Cloud to GitLab.com. We noticed people referred to it already as GitLab.com and we want to prevent confusion. If you want unlimited private repositories and collaborators please...

Some time ago, we released a packaged version of GitLab for super fast and easy installation using Omnibus. To show how easy it is to use GitLab Omnibus and to help you getting started with building your own GitLab packages, we created this screencast...

We are moving the gitlab.org website and this blog to www.gitlab.com and www.gitlab.com/blog. All the content is preserved and all the blog articles still have their comments intact. On www.gitlab.com will be one blog with all our blog posts served...

We heard a few people saying that using a SSH key is hard. In this screencast we show you that adding a SSH key to GitLab is very simple, allowing everyone to push and pull to GitLab without having to enter their username and password every time.

Getting started with Git and Gitlab Screencast

We believe that GitLab is the best way to manage your projects and code. To share our enthusiasm and make GitLab accessible to everyone, we created our first screencast highlighting the basics of starting...

Currently GitLab renders line-breaks in markdown files as line-breaks. We propose to change this behaviour to conform to the markdown specification and only render line-breaks when you end a line with two or more spaces. Paragraphs will continue to...

GitLab is the most fully featured open source application to manage git repositories. However, historically it was not easy to install and update GitLab. Installing it required copy-pasting commands from a long guide. The guide actually worked but...

On July 22, 2013 we introduced GitLab Enterprise Edition (EE). Since then, both EE and the Community Edition have grown and flourished. There are now multiple Fortune 100 companies running the Enterprise Edition and the use of the Community Edition...

We've just published an overview of GitLab High Availability Solutions. The subject of high availability (HA) has come up frequently with our customers. GitLab is a business-critical service for some of our users. We want to meet their concerns in...

We're excited to welcome Marc as an account manager for GitLab. Marc' primary role is getting people to use GitLab. As an account manager, he will be a Point of Contact for GitLab's sales-related activities.

The Changelog podcast interviewed our co-founder Sytse Sijbrandij yesterday. We want to thanks Andrew and Adam of the Changelog for chance to come on the show. In the podcast we discuss the history of GitLab, the introduction of the Enterprise Edition...

As you may have heard already, GitLab Cloud is now running the latest GitLab 5.3 release. You can now view a contributor graph per project, integrate with HipChat and Campfire, tweak permissions on your snippets, and get a Scrum-style overview of the...

As of this week Jacob Vosmaer joins GitLab.com as a senior service engineer. He will be providing support, installation/maintenance and development services for GitLab Cloud and our support and consultancy customers. In addition, he will support the...

Integrating GitLab CI with GitLab to enable distributed builds

The GitLab.com team strongly believes in using feature branches and merge requests in software development. We also think that Test Driven Development (TDD) should be used wherever possible. If you combine these things what follows is that you have to know the testing results of a feature branch before accepting the merge request. GitLab CI was build to offer this functionality and we think most people using GitLab would benefit from using GitLab CI as well.

To make this easier we have now integrated GitLab CI with GitLab. This tight integration offers three great benefits:

You can login to GitLab CI with your GitLab credentials.

The GitLab user interface shown the projects you have access to.

Setting up a testing environment for a new project no longer takes 8 steps but just one.

GitLab Cloud is now running the latest GitLab 5.2 release. You can now fork repos, search the source code, share deploy keys between projects and with turbolinks everything should be faster as well. Enjoy!

This summer Achilleas Pipinellis will work on packaging GitLab for Fedora and RedHat in a Google Summer of Code project. We are very excited and thankful for the support of Fedora and Google. Please see Axilleas his blog post on GitLab.org for more...

GitLab Cloud is now running the latest GitLab 5.1 release. You can now adjust the email notification settings per project and there is a cool new network graph. Everything should be even faster as well. Happy pushing!

People wanted to know how much GitLab.com would cost them when we started charging. We are happy to announce we now have a good answer to that question. Our pricing page contains the details. Highlights include:

Today GitLab.com was upgraded to the latest version. This means our 1.800 users can now use all the features of GitLab 4.0 and GitLab 4.1 One of the best features is namespacing, this was one of the most requested features.

We have great news to share today. Dmitriy Zaporozhets, the lead author of GitLab, joins GitLab.com as a co-founder. He will work full time on Gitlab from now on. In a year GitLab has grown from a small project to more than 10.000 installations. GitLab...

We now have terms of use for Gitlab.com. Please let us know if you have any questions or suggestions. They are based on the terms of use for Wordpress.com which to gratuitously released under a Creative Commons license.

The beta of Gitlab is going well and to date, more than 100 projects were created. People asked about the pricing of Gitlab.com and I would love to hear what you think about this subject. For me the 3 goals of the pricing are:

100 people just got their Gitlab invite in their inbox. More than half of the beta signups now have received an invite. If Gitlab.com stays as stable as the last few days everyone should have an invite in a week from now.

Today we finally send out the invites for the first 10 people. Next week we'll start sending our more invites. We're exited that people will start using the service, I very curious about the feedback. This week I've spend a lot of time testing backup...

Starting today, Marin Jankovski ( @maxlazio) is joining the Gitlab.com team. Marin studied electrical and computer engineering at the University of Novi Sad in Serbia. He is enthusiastic about programming and loves developing in Ruby. He enjoys outdoor...

Since announcing the Gitlab.com plans we've been working on getting everything up and running. Part of this has been exploring the best way to install Gitlab. Although there is a good installation manual it was still a bit of work to set things up...

Within the first five hours since announcing the project, we have received more than 350 signups. To date, more than 500 people signed up for the beta. We are very happy so many people are interested in Gitlab.com and we are working hard to get the...

We added some improvement to keep your repo cleaner. Now you can remove source branch with merge. Just check "Remove source-branch" before accept MR. And source branch will be removed after successful merge

Dashboard:

Commits page:

Project Tab:

Activities (old dashboard page) Click on left link - and Issues page will be loaded(20 last issues assigned to you) Click on left link - and Issues page will be loaded(20 last merge requests assigned to you)