- 28 7月, 2015 1 次提交
-
-
由 Jacob Vosmaer 提交于
https://gitlab.com/gitlab-org/gitlab-git-http-server This change introduces the GITLAB_GRACK_AUTH_ONLY environment variable. When set, Grack requests to GitLab will only respond with the user's GL_ID (if the request is OK) or an error. This allows gitlab-git-http-server to use the main GitLab application as an authentication and authorization backend. If we like how this works we should drop the GITLAB_GRACK_AUTH_ONLY variable at some point in the future.
-
- 27 7月, 2015 1 次提交
-
-
由 Job van der Voort 提交于
Added note about SSH keys being unique Because of issue https://gitlab.com/gitlab-com/support-forum/issues/143 See merge request !1914
-
- 25 7月, 2015 1 次提交
-
-
由 karen Carias 提交于
-
- 24 7月, 2015 2 次提交
-
-
由 Job van der Voort 提交于
Added note about labels in MR because of tweet https://twitter.com/apoirier1/status/624197308759035905 See merge request !1911
-
由 karen Carias 提交于
-
- 22 7月, 2015 12 次提交
-
-
由 Marin Jankovski 提交于
-
由 Job van der Voort 提交于
Added Fork Project document to GitLab Basics See merge request !1909
-
由 Stan Hu 提交于
the repository expire_cache method
-
由 Stan Hu 提交于
Remove 7.14 entry that was pushed to 7.13 See merge request !1020
-
由 Stan Hu 提交于
-
由 Stan Hu 提交于
Fix 404 error in files view after deleting the last file in a repository Here's the logic: 1. In `TreeController`, `require_non_empty_project` will prevent `show` from being called if the project is empty. That means all calls to `show` will be guaranteed to have at least 1 commit. 2. If the ref name is not valid, then return a 404. This ensures that at least the controller is looking at a valid branch/tag/SHA ID. 3. This leaves a number of cases: ``` 3a. Valid ref, valid directory 3b. Valid ref, valid filename 3c. Valid ref, invalid path 3d. Valid ref, no files ``` Case 3a: The tree will not be `empty?` and will pass through the whole function. Case 3b: The tree will be `empty?` but the `blob_at` will resolve properly and trigger a redirect to the file. Case 3c: In this case, a path is given. Return 404 if it cannot be resolved neither as a tree nor a blob. Case 3d: In this case, no path is given. If the tree is empty, this means it's an empty branch and just fall through. Example broken branch: https://gitlab.com/gitlab-org/gitlab-test/tree/empty-branch Closes #1362 See merge request !1010
-
由 karen Carias 提交于
-
由 karen Carias 提交于
-
由 Hannes Rosenögger 提交于
Fix full screen mode for snippet comments ZenMode is now initialized for snippet pages. Fixes #2036. See merge request !1016
-
由 Stan Hu 提交于
Closes #1362
-
由 Daniel Gerhardt 提交于
ZenMode is now initialized for snippet pages. Fixes #2036.
-
- 21 7月, 2015 11 次提交
-
-
由 Valery Sizov 提交于
You need to store your DB encryption key You can break two-factor authentication for existing users when restoring a backup if you lost your DB encryption key. See merge request !1015
-
由 Jacob Vosmaer 提交于
-
由 Valery Sizov 提交于
Update changelog See merge request !1013
-
由 Valery Sizov 提交于
-
由 Valery Sizov 提交于
Don't stop if database.sql.gz already exists The existing behavior of the backups is to overwrite whatever data was still there in the scratch directories. This broke when we added a 'gzip' step because 'gzip database.sql' will fail if 'database.sql.gz' already exists. Doing 'rm -f database.sql.gz' before the 'gzip' avoids this failure. See merge request !1011
-
由 Jacob Vosmaer 提交于
The existing behavior of the backups is to overwrite whatever data was still there in the scratch directories. This broke when we added a 'gzip' step because 'gzip database.sql' will fail if 'database.sql.gz' already exists. Doing 'rm -f database.sql.gz' before the 'gzip' avoids this failure.
-
由 Robert Schilling 提交于
Fix change log for 7.11 and move entry to 7.12 The change log for 7.11 was accidentally split in 3865a1d9. Additionally, the change added with this commit did not make it into 7.11 according to `git branch --contains` and it has not been cherry picked to 7-11-stable so the entry is moved to 7.12. Refs GH-5625, GH-9318. See merge request !1009
-
由 Daniel Gerhardt 提交于
The change log for 7.11 was accidentally split in 3865a1d9. Additionally, the change added with this commit did not make it into 7.11 according to `git branch --contains` and it has not been cherry picked to 7-11-stable so the entry is moved to 7.12. Refs GH-5625, GH-9318. [ci skip]
-
由 Stan Hu 提交于
GoogleCode importer: Do not care about casing of image file extensions When a GoogleCode repository contains an attached image with an UPPERCASE file extension, it's not inlined. /CC @DouweM See merge request !1003
-
由 Stan Hu 提交于
Fix (i.e. prevent) access to disabled features for unauthenticated users Unauthenticated users had access to disabled features of public projects. The code has been slightly refactored so that feature checks are done in a separate method and can also be applied for public access. See merge request !1006
-
由 Stan Hu 提交于
merge_requests: add fetch command to the MR page In our instance, users asked for an easy way to get the contents of the MR into their local clone. This adds a command line which can be used to fetch the contents of the MR. Screenshot: ![fetch-command](https://gitlab.com/gitlab-org/gitlab-ce/uploads/d83acfbdb69f023d13b45dff5d583ac1/fetch-command.png) See merge request !678
-
- 20 7月, 2015 12 次提交
-
-
由 Ben Boeckel 提交于
-
由 Valery Sizov 提交于
Remove repository graph log to fix slow cache updates after push event Recalculating `graph_log` took minutes on a large repository since each of the 6000 commits would need to calculate the diff. Since graph_log does not appear to be used, remove it from the list of things to update. For the Linux kernel repository, this reduced the `ProjectCacheWorker` time from 8+ minutes to 16 seconds. Closes #2016 See merge request !1005
-
由 Valery Sizov 提交于
Remove redundant last push event if activity feed is set to main page ### What does this MR do? This MR eliminates a redundant last push event message if the user's preferences are set to the main activity feed. ### Why was this MR needed? Lots of wasted space was introduced as a result. ### Screenshots #### Before ![image](https://gitlab.com/stanhu/gitlab-ce/uploads/e7fdeb58b2017ec45443bf0d54a94685/image.png) #### After ![image](https://gitlab.com/stanhu/gitlab-ce/uploads/d4a15113127be119e7c33ff501020f16/image.png) ### What are the relevant issue numbers? Closes #2009 See merge request !995
-
由 Valery Sizov 提交于
Public project activity page asks for sign-in https://gitlab.com/gitlab-org/gitlab-ce/issues/2021 See merge request !1007
-
由 Marin Jankovski 提交于
-
由 Valery Sizov 提交于
-
由 Jacob Vosmaer 提交于
Use whoami instead of $USER
-
由 Marin Jankovski 提交于
Set OmniAuth full_host parameter to ensure redirect URIs are correct ### What does this MR do? This MR sets the OmniAuth `full_host` parameter to the configured GitLab URL to ensure the `redirect_uri` parameter is called with the right GitLab host. ### Why was this MR needed? [OmniAuth attempts to grab the request URI](http://awesomeprogrammer.com/blog/2012/12/09/dealing-with-omniauth-redirect-uri-mismatch-invalid-port-number-gotcha/) and use that. If you set up a reverse proxy that terminates SSL at the Web server layer (e.g. https://gitlab.domain.com), omniauth will use the internal URL (e.g. http://my-host:8080) in its redirect URI unless all the Web server headers are properly set (e.g. `X-Forwarded-Port`, etc.). This is easy to forget or mess up, and it's better to ensure that OmniAuth has the right value from the start. ### What are the relevant issue numbers? Closes #1967 See merge request !991
-
由 Daniel Gerhardt 提交于
Unauthenticated users had access to disabled features of public projects. The code has been slightly refactored so that feature checks are done in a separate method and can also be applied for public access.
-
由 Stan Hu 提交于
Recalculating graph_log took minutes on a large repository since each of the 6000 commits would need to calculate the diff. Since graph_log does not appear to be used, remove it from the list of things to update. For the Linux kernel repository, this reduced the ProjectCacheWorker time from 8+ minutes to 16 seconds. Closes #2016
-
由 Stan Hu 提交于
Fix label read access for unauthenticated users The label page was added to navigation for unauthorized users because the previously used milestone read permission was still checked. This has been fixed and read access to labels is now granted (again) for public projects. This regression has been introduced in 07efb17e (7.12). See also 9bcd3639. Refs !836, !842. See merge request !1000
-
由 Sven Strickroth 提交于
Signed-off-by: NSven Strickroth <email@cs-ware.de>
-