- 21 11月, 2016 2 次提交
-
-
由 Yorick Peterse 提交于
Initializing Rugged objects is way too expensive just to check if a repository exists. Even though we cache this data once in a while we have to refresh this. On GitLab.com we have seen Repository#exists? taking up to _1 minute_ to complete in the absolute worst case, though usually it sits around a second or so. Using File.exist? to instead check if $GIT_DIR/refs exists is a much faster way of checking if a repository was initialized properly.
-
由 Yorick Peterse 提交于
This moves the logic of detecting special repository files (e.g. a README or a Koding configuration file) to a single class: Gitlab::FileDetector. Moving this logic into a single place allows this to be re-used more easily. This commit also changes Repository#gitlab_ci_yaml so that its cached similar to other data (e.g. the Koding configuration file).
-
- 18 11月, 2016 1 次提交
-
-
由 Adam Niedzielski 提交于
We need to handle annotated tags that are created via GitLab UI. Annotated tags have their own SHA. We have to pass this SHA to post-receive hook to mirror what happens when someone creates an annotated tag in their local repository and pushes it via command line. In order to obtain tag SHA we first have to create it. This is a bit confusing because we create the tag before executing pre-hooks, but there is no way to create a tag outside the repository. If pre-hooks fail we have to clean up after ourselves.
-
- 16 11月, 2016 2 次提交
-
-
由 Nick Thomas 提交于
gitlab-shell v3.6.6 would give project paths like so: * namespace/project gitlab-shell v4.0.0 can give project paths like so: * /namespace1/namespace2/project * /namespace/project * /path/to/repository/storage/namespace1/namespace2/project * /path/to/repository/storage/namespace/project
-
由 Valery Sizov 提交于
-
- 11 11月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 09 11月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 08 11月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-
- 07 11月, 2016 1 次提交
-
-
由 Grzegorz Bizon 提交于
-
- 29 10月, 2016 1 次提交
-
-
由 Alejandro Rodríguez 提交于
When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing to the sha of the tag to the sha of the commit the tag points to. The problem is that only annotated tags have `object_sha`s, lightweight tags don't (it's nil), so (only) in their case we still need to use `tag.target`.
-
- 28 10月, 2016 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 24 10月, 2016 1 次提交
-
-
由 Stan Hu 提交于
After a project import, there's a chance that the UI checks the branch count before the project has been imported. This change causes more of the keys to be flushed after an import and forces a rebuild of the repository cache. Closes #13518
-
- 14 10月, 2016 1 次提交
-
-
由 Z.J. van de Weg 提交于
-
- 11 10月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 10 10月, 2016 2 次提交
-
-
由 Adam Niedzielski 提交于
Fixes #21800.
-
由 tiagonbotelho 提交于
-
- 04 10月, 2016 1 次提交
-
-
由 Z.J. van de Weg 提交于
-
- 20 9月, 2016 1 次提交
-
-
由 Dan Dunckel 提交于
-
- 14 9月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-
- 07 9月, 2016 3 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
- 02 9月, 2016 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 01 9月, 2016 1 次提交
-
-
由 Stan Hu 提交于
If `git gc` runs and `Repository` has an instance to `Rugged::Repository`, a bug in libgit2 may cause the instance to return a stale value or a missing branch. This change not only optimizes the branch lookup so we don't have to iterate through every branch, but it also works around the `git gc` issue by forcing a repository reload every time `Repository#find_branch` is called. See: https://github.com/libgit2/libgit2/issues/1534 Closes #15392, #21470
-
- 19 8月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
- It sets the `in_progress_merge_commit_sha` variable on the given merge request, so that the branch permissions (developers can merge) check can proceed in the `pre-receive` hook.
-
- 09 8月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 03 8月, 2016 1 次提交
-
-
由 Paco Guzman 提交于
So we have raw_diffs too
-
- 29 7月, 2016 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 27 7月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
Project and branch cache is expired when project is still empty or new branch is created. develops tests accordingly Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 25 7月, 2016 1 次提交
-
-
由 Alejandro Rodríguez 提交于
This reverts merge request !5375
-
- 22 7月, 2016 2 次提交
-
-
由 Stan Hu 提交于
We were seeing a number of error messages when attempting to create a keep-around ref: 1. Failed to create locked file `refs/keep-around/XYZ`: File exists 2. Failed to write reference `refs/keep-around/XYZ`: a reference with that name already exists. I'm not sure how these happen, but I suspect when multiple workers attempt to write the same file we may have an issue. The force parameter should help ensure the file gets created, as well as the rescues to prevent 500 Errors. Rugged/libgit2 unfortunately do not allow you to delete or re-create a reference that has been corrupted, even with the force parameter. Closes #20109
-
由 Alejandro Rodríguez 提交于
-
- 21 7月, 2016 1 次提交
-
-
Replace invocation of `find` with Ruby code that matches old cached files in a better, and safe way to avoid data-integrity issues.
-
- 20 7月, 2016 1 次提交
-
-
由 Paco Guzman 提交于
-
- 19 7月, 2016 2 次提交
-
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
- 18 7月, 2016 2 次提交
-
-
由 tiagonbotelho 提交于
-
由 Rémy Coutable 提交于
This reverts commit 530f5158. See !4892. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 14 7月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
This reverts commit 9ca633eb, reversing changes made to fb229bbf.
-
- 13 7月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
1. When a merge request is being merged, save the merge commit SHA in the `in_progress_merge_commit_sha` database column. 2. The `pre-receive` hook looks for any locked (in progress) merge request with `in_progress_merge_commit_sha` matching the `newrev` it is passed. 3. If it finds a matching MR, the merge is legitimate. 4. Update `git_access_spec` to test the behaviour we added here. Also refactored this spec a bit to make it easier to add more contexts / conditions.
-