- 12 5月, 2018 2 次提交
-
-
由 Joshua Lambert 提交于
-
由 Robert Speicher 提交于
-
- 11 5月, 2018 2 次提交
-
-
由 Achilleas Pipinellis 提交于
Fix: API Documentation typo on Microsoft Teams slug See merge request gitlab-org/gitlab-ee!5412
-
由 Maxime 提交于
-
- 10 5月, 2018 4 次提交
-
-
由 Mark Fletcher 提交于
- Document Registation - POST `/runners/` - Document Deletion - DELETE `/runners/` - Document Verification - POST `/runners/verify/
-
由 Stan Hu 提交于
Adding the :prometheus tag to an rspec test will clear out memory-mapped files and reset the registry. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/39968
-
由 Brendan O'Leary 🐢 提交于
-
-
- 09 5月, 2018 3 次提交
-
-
-
由 Marcia Ramos 提交于
-
由 Lin Jen-Shin 提交于
* Re-apply changes from https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9666 * Update the wordings accordingly for the current revision * Update the example to make it less confusing
-
- 08 5月, 2018 7 次提交
-
-
由 Gilbert Roulot 提交于
-
由 James Lopez 提交于
-
由 Dylan Griffith 提交于
-
由 Dylan Griffith 提交于
-
由 Dylan Griffith 提交于
-
由 Marcia Ramos 提交于
-
由 Filipa Lacerda 提交于
-
- 07 5月, 2018 13 次提交
-
-
由 Tomasz Maczukin 提交于
-
由 Clement Ho 提交于
-
由 Joshua Lambert 提交于
-
由 Tiago Botelho 提交于
-
由 Tiago Botelho 提交于
-
由 Filipa Lacerda 提交于
-
由 Kamil Trzciński 提交于
-
由 Toon Claes 提交于
-
由 Toon Claes 提交于
No idea where it used to be, but I can no longer find it.
-
由 Toon Claes 提交于
-
由 Filipa Lacerda 提交于
-
由 Shinya Maeda 提交于
-
由 Joshua Lambert 提交于
-
- 04 5月, 2018 4 次提交
-
-
由 Mark Fletcher 提交于
-
由 Bob Van Landuyt 提交于
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 提交于
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.
-
由 Winnie Hellmann 提交于
-
- 03 5月, 2018 1 次提交
-
-
由 Mayra Cabrera 提交于
-
- 02 5月, 2018 2 次提交
-
-
-
由 Mike Greiling 提交于
-
- 01 5月, 2018 2 次提交
-
-
由 James Ramsay 提交于
LFS can be enabled and disabled per project using the API by Masters and Owners, but the UI is only available to Admins. The interface and API should be consistent. LFS can also be enabled and disabled per group using the API by Owners, but the UI is only available to Admins. This interface should also be consistent. Additionally removes an unneeded check if 2FA interface, since the interface is only available to Owners. Closes #33320
-
由 Jan Provaznik 提交于
-