Jacob Schatz 132e3f5471 Merge branch 'register-tab' into 'master' ... Only show register tab if signup enabled. ## What does this MR do? Fixes a regression where the register tab is activated, even if sign-up enabled is not activated in application_settings. ## Screenshots (if relevant) When signup is disabled:  ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG.md) entry added - [ ] All builds are passing - [x] 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 it does - 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? https://gitlab.com/gitlab-org/gitlab-ce/issues/23654 See merge request !7058		2016-10-25 02:47:27 +00:00
..
confirmations	Use Ruby 1.9 syntax in tab_single def and usage.	2016-10-15 08:28:54 +02:00
mailer	…
passwords	Use Ruby 1.9 syntax in tab_single def and usage.	2016-10-15 08:28:54 +02:00
registrations	…
sessions	Merge branch 'master' into sign_in_forgot_password	2016-10-22 14:51:59 -05:00
shared	Only show register tab if signup enabled.	2016-10-24 17:50:19 +02:00
unlocks	Use Ruby 1.9 syntax in tab_single def and usage.	2016-10-15 08:28:54 +02:00