- 07 May, 2018 4 commits
-
-
Tiago Botelho authored
-
Tiago Botelho authored
-
Tim Zallmann authored
-
Marc authored
-
- 06 May, 2018 1 commit
-
-
Phil Hughes authored
-
- 04 May, 2018 25 commits
-
-
Paul Slaughter authored
-
Phil Hughes authored
hide success message when staging files improve action button hover
-
Kushal Pandya authored
-
Mario de la Ossa authored
-
Bob Van Landuyt authored
-
Tiago Botelho authored
-
James Edwards-Jones authored
-
Phil Hughes authored
fixed form collapsing too soon
-
James Lopez authored
-
Phil Hughes authored
-
Douwe Maan authored
Ensure web hook 'blocked URL' errors are stored in as web hook logs and properly surfaced to the user
-
Dylan Griffith authored
As described in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18738 there is a problem and the larger fix may take longer so we can just revert this small change for now
-
Phil Hughes authored
i18n
-
Bob Van Landuyt authored
`InternalRedirect` prevents Open redirect issues by only allowing redirection to paths on the same host. It cleans up any unwanted strings from the path that could point to another host (fe. //about.gitlab.com/hello). While preserving the querystring and fragment of the uri. It is already used by: - `TermsController` - `ContinueParams` - `ImportsController` - `ForksController` - `SessionsController`: Only for verifying the host in CE. EE allows redirecting to a different instance using Geo.
-
Bob Van Landuyt authored
This enforces the terms in the web application. These cases are specced: - Logging in: When terms are enforced, and a user logs in that has not accepted the terms, they are presented with the screen. They get directed to their customized root path afterwards. - Signing up: After signing up, the first screen the user is presented with the screen to accept the terms. After they accept they are directed to the dashboard. - While a session is active: - For a GET: The user will be directed to the terms page first, after they accept the terms, they will be directed to the page they were going to - For any other request: They are directed to the terms, after they accept the terms, they are directed back to the page they came from to retry the request. Any information entered would be persisted in localstorage and available on the page.
-
Bob Van Landuyt authored
When a user accepts, we store this in the agreements to keep track of which terms they accepted. We also update the flag on the user.
-
Bob Van Landuyt authored
When terms are present, they can be viewed on `/-/users/terms`.
-
Bob Van Landuyt authored
We will reuse the the dropdown, but exclude some menu items based on permissions. So moving the menu to a partial, and adding checks for each menu item here.
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
This allows admins to define terms in the application settings. Every time the terms are adjusted, a new version is stored and becomes the 'active' version. This allows tracking which specific version was accepted by a user.
-
Bob Van Landuyt authored
That way we can link a users acceptance of terms directly to a terms record.
-
Phil Hughes authored
instead of taking over whole sidebar, it now just shows over the commit box after 5 seconds the commit box goes back to its compact logic
-
Phil Hughes authored
long branch names no longer wrap
-
George Tsiolis authored
-
George Tsiolis authored
-
- 03 May, 2018 10 commits
-
-
Filipa Lacerda authored
-
Filipa Lacerda authored
-
Jose authored
-
Robert Speicher authored
This drastically reduces page load times at gitlab.com scale.
-
Dylan Griffith authored
-
Phil Hughes authored
fixed review mode not being editable
-
Phil Hughes authored
-
Dylan Griffith authored
-
Dylan Griffith authored
-
George Tsiolis authored
-