- 01 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 27 Jul, 2017 3 commits
-
-
Alexis Reigel authored
-
Alexis Reigel authored
other than just removing a key, which doesn't affect the verified state of a commit, revoking a key unverifies all signed commits.
-
Alexis Reigel authored
-
- 13 Jul, 2017 1 commit
-
-
Robin Bobbitt authored
When sign-in is disabled: - skip password expiration checks - prevent password reset requests - don’t show Password tab in User Settings - don’t allow login with username/password for Git over HTTP requests - render 404 on requests to Profiles::PasswordsController
-
- 25 Jun, 2017 1 commit
-
-
James Lopez authored
-
- 23 Jun, 2017 11 commits
-
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
- 06 Jun, 2017 1 commit
-
-
blackst0ne authored
Add a rubocop rule to check if a method 'redirect_to' is used without explicitly set 'status' in 'destroy' actions of controllers
-
- 05 Jun, 2017 1 commit
-
-
Z.J. van de Weg authored
This is the first commit doing mainly 3 things: 1. create a new scope and allow users to use it 2. Have the JWTController respond correctly on this 3. Updates documentation to suggest usage of PATs There is one gotcha, there will be no support for impersonation tokens, as this seems not needed. Fixes gitlab-org/gitlab-ce#19219
-
- 10 May, 2017 1 commit
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 06 Apr, 2017 3 commits
-
-
Alexis Reigel authored
-
Markus Koller authored
-
Markus Koller authored
-
- 31 Mar, 2017 1 commit
-
-
Tiago Botelho authored
-
- 17 Mar, 2017 1 commit
-
- 15 Mar, 2017 1 commit
-
- 07 Mar, 2017 1 commit
-
-
Markus Koller authored
-
- 06 Mar, 2017 1 commit
-
-
Tiago Botelho authored
-
- 03 Mar, 2017 1 commit
-
-
Pawel Chojnacki authored
-
- 01 Mar, 2017 1 commit
-
-
Tiago Botelho authored
-
- 28 Feb, 2017 1 commit
-
-
Tiago Botelho authored
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 15 Feb, 2017 1 commit
-
-
Annabel Dunstone Gray authored
-
- 01 Feb, 2017 1 commit
-
-
Richard Macklin authored
in Profiles::NotificationsController#update
-
- 16 Dec, 2016 2 commits
-
-
Drew Blessing authored
The two factor authentication account string only had the user's email address. This led to ambiguous entries in two factor code generating apps. This adds the GitLab host to the account string in the standard format (according to Google). No matter the code generator this change disambiguates the entry.
-
Timothy Andrew authored
-
- 23 Nov, 2016 1 commit
-
-
Yorick Peterse authored
Flushing the events cache worked by updating a recent number of rows in the "events" table. This has the result that on PostgreSQL a lot of dead tuples are produced on a regular basis. This in turn means that PostgreSQL will spend considerable amounts of time vacuuming this table. This in turn can lead to an increase of database load. For GitLab.com we measured the impact of not using events caching and found no measurable increase in response timings. Meanwhile not flushing the events cache lead to the "events" table having no more dead tuples as now rows are only inserted into this table. As a result of this we are hereby removing events caching as it does not appear to help and only increases database load. For more information see the following comment: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
-
- 17 Nov, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-