- 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 4 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 16 Nov, 2016 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 18 Aug, 2016 2 commits
-
-
Timothy Andrew authored
1. Remove an unnecessary (since we're fetching all the records anyway) `pluck` while fetching U2F registration records. 2. Align "Your device was successfully set up!" section with the "U2F Devices" table below.
-
Timothy Andrew authored
1. Display a list of U2F devices on the `two_factor_auth` page. 2. Allow deleting individual U2F devices. 3. Allow setting a (optional) name for a device (during registration).
-
- 08 Aug, 2016 1 commit
-
-
Carlos Ribeiro authored
-
- 14 Jul, 2016 1 commit
-
-
Timothy Andrew authored
1. Only on supported Chrome versions 2. Mainly, this lets us simplify the javascript-based U2F check to `window.u2f`, where `window.u2f` can either be loaded from the GitLab server (for Chrome) or from the Firefox extension. 3. This is a better way to provide browser detection for U2F.
-
- 17 Jun, 2016 1 commit
-
-
Felipe Artur authored
-
- 16 Jun, 2016 3 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
Timothy Andrew authored
- Extract a duplicated `redirect_to` - Fix a typo: "token", not "certificate" - Have the "Expires at" datepicker be attached to a text field, not inline - Have both private tokens and personal access tokens verified in a single "authenticate_from_private_token" method, both in the application and API. Move relevant logic to `User#find_by_personal_access_token` - Remove unnecessary constants relating to API auth. We don't need a separate constant for personal access tokens since the param is the same as for private tokens.
-
- 14 Jun, 2016 1 commit
-
-
Patricio Cano authored
-
- 10 Jun, 2016 2 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
- 09 Jun, 2016 1 commit
-
-
Timothy Andrew authored
- No hardcoded colors in any SCSS file except `variables.scss` - Don't allow choosing a date in the past - Use the same table as in the "Applications" tab - The button should say "Create Personal Access Token" - Float the revoke button to the right of the table cell - Change the revocation message to be more explicit. - Date shouldn't look selected on page load - Don't use a panel for the created token - Use a normal flash for "Your new personal access token has been created" - Show the input (with the token) below it full width. - Put the "Make sure you save it - you won't be able to access it again." message near the input - Have the created token's input highlight all on single click
-
- 06 Jun, 2016 1 commit
-
-
Timothy Andrew authored
- Move the `TwoFactorAuthsController`'s `new` action to `show`, since the page is not used to create a single "two factor auth" anymore. We can have a single 2FA authenticator app, along with any number of U2F devices, in any combination, so the page will be accessed after the first "two factor auth" is created. - Add the `u2f` javascript library, which provides an API to the browser's U2F implementation. - Add tests for the JS components
-
- 03 Jun, 2016 1 commit
-
-
James Lopez authored
This reverts commit 3e991230.
-