An error occurred fetching the project authors.
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 19 Jun, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 06 Jun, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 30 May, 2017 1 commit
-
-
Phil Hughes authored
-
- 24 May, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 18 May, 2017 3 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Sometimes, new references are not retrieved when a `git fetch` is called in a bare repos. The easiest solution is to cleanup the test repos and retry in this case. This only happens when a new ref is added to TestEnv::BRANCH_SHA or TestEnv::FORKED_BRANCH_SHA. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 15 May, 2017 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
It seems that bad things happen when two gRPC stubs share one gRPC channel so let's stop doing that. The downside of this is that we create more gRPC connections; one per stub.
-
- 28 Apr, 2017 1 commit
-
-
Sam Rose authored
-
- 19 Apr, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 11 Apr, 2017 3 commits
-
-
Phil Hughes authored
-
Alejandro Rodríguez authored
-
Luke "Jared" Bennett authored
-
- 02 Apr, 2017 2 commits
-
-
Bob Van Landuyt authored
fixes the warning: fatal: destination path '~/gitlab-ce/gitlab/tmp/tests/gitlab-test-fork_bare' already exists and is not an empty directory.
-
Stan Hu authored
Closes #30347
-
- 31 Mar, 2017 3 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Also disabled assets warming for Capybara/RSpec and remove a check to skip assets warming when ./tmp/cache/assets/test exists because assets are now served by webpack-dev-server. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 30 Mar, 2017 2 commits
-
-
Nick Thomas authored
-
Rémy Coutable authored
Use full path for moving directories when changing namespace path See merge request !2078
-
- 23 Mar, 2017 1 commit
-
-
Sanster authored
-
- 03 Mar, 2017 1 commit
-
-
Alejandro Rodríguez authored
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
- 23 Feb, 2017 4 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
Douwe Maan authored
-
- 03 Feb, 2017 1 commit
-
-
Sean McGivern authored
Backport changes from the EE-only squash implementation, which would otherwise conflict when merge CE into EE. <https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1024>
-
- 19 Jan, 2017 1 commit
-
-
jurre authored
-
- 14 Nov, 2016 1 commit
-
-
Stan Hu authored
Steps to reproduce: 1. Start with a repo with an image 2. Add a commit to delete the image 3. Add another commit to replace the image with another image In a diff comparison, we really just compare about what the image was before the diff, not the direct parent of the last commit. This MR fixes that. Closes #3893, gitlab-org/gitlab-ee#678 Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 10 Nov, 2016 1 commit
-
-
Adam Niedzielski authored
In this case comparing old_path and new_path is not enough because there are two entires that match.
-
- 07 Nov, 2016 1 commit
-
-
Nick Thomas authored
Previously, we were calling `git update-ref <ref> <sha>` about 30 times per test using `create(:project)` or similar.
-
- 17 Oct, 2016 1 commit
-
-
Valery Sizov authored
-
- 15 Oct, 2016 1 commit
-
- 13 Oct, 2016 1 commit
-
-
Sean McGivern authored
-
- 09 Oct, 2016 1 commit
-
-
tiagonbotelho authored
-
- 30 Aug, 2016 1 commit
-
-
Sean McGivern authored
Forks may not be up-to-date with the target project, and so might not contain one of the parent refs in their repo. Fetch this if it isn't present.
-
- 25 Aug, 2016 1 commit
-
-
Sean McGivern authored
These can't be resolved in the UI because if they aren't in a UTF-8 compatible encoding, they can't be rendered as JSON. Even if they could, we would be implicitly changing the file encoding anyway, which seems like a bad idea.
-
- 12 Aug, 2016 1 commit
-
-
Sean McGivern authored
-