Find a file
Annabel Dunstone Gray 1fed97530a Merge branch 'AshleyDumaine/gitlab-ce-22494-wide-custom-header-logos-arent-centered' into 'master'
Center the header logo

_Originally opened at !6507 by @AshleyDumaine._

- - -

## What does this MR do?

* Centers the header logo using `relative` positioning on the svg or img in the header-logo

## Are there points in the code the reviewer needs to double check?

## Why was this MR needed?

The custom wide header logos aren't centered after logging in as seen in #22494

## Screenshots (if relevant)

| Before | After |
| --------- | ------ |
| ![Screen_Shot_2016-09-24_at_3.35.26_PM](/uploads/576db77e0eb299b06d2a5abf341f058f/Screen_Shot_2016-09-24_at_3.35.26_PM.png) | ![Screen_Shot_2016-09-24_at_3.35.51_PM](/uploads/47237b6c28d438a6f255dffb8b3d39d4/Screen_Shot_2016-09-24_at_3.35.51_PM.png) |

Signout (for centering comparison):
![Screen_Shot_2016-09-24_at_3.35.59_PM](/uploads/4484313ff5841774769c4737584af7fc/Screen_Shot_2016-09-24_at_3.35.59_PM.png)

## Does this MR meet the acceptance criteria?

- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- Tests
  - [x] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

## What are the relevant issue numbers?

Closes #22494

See merge request !6610
2016-10-01 19:57:18 +00:00
.github
.gitlab
app Merge branch 'AshleyDumaine/gitlab-ce-22494-wide-custom-header-logos-arent-centered' into 'master' 2016-10-01 19:57:18 +00:00
bin
builds
changelogs
config Merge branch 'initialize-redis' into 'master' 2016-09-30 12:32:18 +00:00
db Improvements to user organization field feature after code review 2016-09-27 14:04:39 +03:00
doc Merge branch 'cs-frontend-guidelines' into 'master' 2016-10-01 11:14:58 +00:00
docker
features Add organization field to user profile 2016-09-27 14:04:39 +03:00
fixtures/emojis
generator_templates/active_record/migration
lib Merge branch '21744-fix-missing-values-in-linter' into 'master' 2016-09-30 16:51:47 +00:00
log
public Merge branch 'patch-3' into 'master' 2016-09-26 14:02:39 +00:00
rubocop
scripts Reduce output to the build log 2016-09-28 09:16:09 +02:00
shared
spec Changed zero padded days to no padded days in date_format 2016-10-01 12:18:44 -05:00
tmp
vendor Update templates for 8.13 2016-09-30 12:16:41 +02:00
.csscomb.json
.flayignore Tell Flay to ignore Gitlab::Diff::PositionTracer 2016-09-27 14:31:33 +02:00
.foreman
.gitattributes Removed lfs 2016-09-27 19:54:54 +01:00
.gitignore
.gitlab-ci.yml Remove Flog as we use a Rubocop that does its job. 2016-09-28 19:38:43 -06:00
.haml-lint.yml
.mailmap
.pkgr.yml Update .pkgr.yml with Ubuntu 16.04 dependencies 2016-09-20 17:35:49 +02:00
.rspec
.rubocop.yml Revert "Merge branch 'rs-update-rubocop-rspec' into 'master'" 2016-09-21 14:32:25 +03:00
.rubocop_todo.yml
.ruby-version
.scss-lint.yml
.vagrant_enabled
CHANGELOG Merge branch 'AshleyDumaine/gitlab-ce-22494-wide-custom-header-logos-arent-centered' into 'master' 2016-10-01 19:57:18 +00:00
config.ru
CONTRIBUTING.md Merge branch 'sh-add-link-to-reliable-capybara-specs' into 'master' 2016-09-16 09:46:07 +00:00
doc_styleguide.md
docker-compose.yml
Gemfile fix broken repo 500 errors in UI and added relevant specs 2016-09-29 16:58:14 +02:00
Gemfile.lock fix broken repo 500 errors in UI and added relevant specs 2016-09-29 16:58:14 +02:00
GITLAB_SHELL_VERSION Use gitlab-shell v3.6.2 (GIT TRACE logging) 2016-09-26 10:03:27 +02:00
GITLAB_WORKHORSE_VERSION Use gitlab-workhorse 0.8.2 2016-09-16 14:30:36 +02:00
LICENSE
MAINTENANCE.md
PROCESS.md
Procfile
Rakefile
README.md Fix typo in README 2016-09-25 16:11:18 +00:00
VERSION Update VERSION to 8.13.0-pre 2016-09-22 17:39:25 +02:00

GitLab

build status 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.