Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

gitlab-foss

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Lin Jen-Shin authored
    * upstream/master: (221 commits)
      Differentiate the expire from leave event
      Use LabelsFinder on Fogbuz importer
      Use LabelsFinder on Google Code importer
      Change the order of tested methods in project_members_controller_spec
      Remove show_menu_above attribute from issuable dropdowns.
      Spaces before `}`!
      Avoid touch label links that does not belongs to project when moving it
      Remove order by label type on LabelsFinder
      Rename Labels::CreateService to Labels::FindOrCreateService
      Add self.project_foreign_key on both Issue and MergeRequest
      Only show label type for projects that belong to a group
      Disable subscribing to group-level labels
      Remove unused method Project#all_labels
      Update specs to cope with new label types and priorities
      Fix max number of permitted priorities per project label
      Fix GitHub importer spec
      Update CHANGELOG
      Add support to group labels to SlashCommands::InterpretService
      Use join instead of subquery on Label.unprioritized scope
      Warn user deleting a group label affect all projects within the group
      ...
    e5de4c77
    History

    GitLab

    Build status CE coverage report Code Climate Core Infrastructure Initiative Best Practices

    Canonical source

    The canonical source of GitLab Community Edition is hosted on GitLab.com.

    Open source software to collaborate on code

    To see how GitLab looks please see the features page on our website.

    • Manage Git repositories with fine grained access controls that keep your code secure
    • Perform code reviews and enhance collaboration with merge requests
    • Each project can also have an issue tracker and a wiki
    • Used by more than 100,000 organizations, GitLab is the most popular solution to manage Git repositories on-premises
    • Completely free and open source (MIT Expat license)
    • Powered by Ruby on Rails

    Hiring

    We're hiring developers, support people, and production engineers all the time, please see our jobs page.

    Editions

    There are two editions of GitLab:

    • GitLab Community Edition (CE) is available freely under the MIT Expat license.
    • GitLab Enterprise Edition (EE) includes extra features that are more useful for organizations with more than 100 users. To use EE and get official support please become a subscriber.

    Website

    On about.gitlab.com you can find more information about:

    Requirements

    Please see the requirements documentation for system requirements and more information about the supported operating systems.

    Installation

    The recommended way to install GitLab is with the Omnibus packages on our package server. Compared to an installation from source, this is faster and less error prone. Just select your operating system, download the respective package (Debian or RPM) and install it using the system's package manager.

    There are various other options to install GitLab, please refer to the installation page on the GitLab website for more information.

    You can access a new installation with the login root and password 5iveL!fe, after login you are required to set a unique password.

    Install a development environment

    To work on GitLab itself, we recommend setting up your development environment with the GitLab Development Kit. If you do not use the GitLab Development Kit you need to install and setup all the dependencies yourself, this is a lot of work and error prone. One small thing you also have to do when installing it yourself is to copy the example development unicorn configuration file:

    cp config/unicorn.rb.example.development config/unicorn.rb

    Instructions on how to start GitLab and how to run the tests can be found in the development section of the GitLab Development Kit.

    Software stack

    GitLab is a Ruby on Rails application that runs on the following software:

    • Ubuntu/Debian/CentOS/RHEL
    • Ruby (MRI) 2.3
    • Git 2.7.4+
    • Redis 2.8+
    • MySQL or PostgreSQL

    For more information please see the architecture documentation.

    Third-party applications

    There are a lot of third-party applications integrating with GitLab. These include GUI Git clients, mobile applications and API wrappers for various languages.

    GitLab release cycle

    For more information about the release process see the release documentation.

    Upgrading

    For upgrading information please see our update page.

    Documentation

    All documentation can be found on doc.gitlab.com/ce/.

    Getting help

    Please see Getting help for GitLab on our website for the many options to get help.

    Is it any good?

    Yes

    Is it awesome?

    Thanks for asking this question Joshua. These people seem to like it.