An error occurred fetching the project authors.
- 12 Jul, 2019 1 commit
-
-
Aleksei Lipniagov authored
Log memory stats after running each spec file and compile the report.
-
- 27 Jun, 2019 1 commit
-
-
Paul Okstad authored
-
- 14 Jun, 2019 1 commit
-
-
Zeger-Jan van de Weg authored
Prior to this change, the hooks directory got cleared. That works, but is not the way to go about it as there's a better way. Setting the env var this commits sets.
-
- 17 May, 2019 1 commit
-
-
Nick Thomas authored
The golang indexer is supplanting the Ruby one in GitLab 12.1, so it's important that we gain confidence in it by using it in the tests now. This should also help to expose problems and catch regressions earlier.
-
- 16 May, 2019 1 commit
-
-
Nick Thomas authored
-
- 13 Mar, 2019 2 commits
-
-
Nick Thomas authored
-
Nick Thomas authored
-
- 27 Feb, 2019 1 commit
-
-
Jacob Vosmaer authored
-
- 23 Feb, 2019 1 commit
-
-
Heinrich Lee Yu authored
Removes unneeded params from permitted list This also fixes commenting on commits with a hash starting with a large number
-
- 23 Jan, 2019 1 commit
-
-
Nick Thomas authored
-
- 27 Dec, 2018 2 commits
-
-
Francisco Javier López authored
This is a port of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23812, which fixes a bug with commenting on LFS image files.
-
Francisco Javier López authored
This commit, introduced in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23812, fixes a problem creating a displaying image diff notes when the image is stored in LFS. The main problem was that `Gitlab::Diff::File` was returning an invalid valid in `text?` for this kind of files. It also fixes a rendering problem with other LFS files, like text ones. They LFS pointer shouldn't be shown when LFS is enabled for the project, but they were.
-
- 07 Dec, 2018 1 commit
-
-
Mark Chao authored
Analyze new commits graph to determine each commit's merge commit. Fix "merged with [commit]" info for merge requests being merged automatically by other actions. Allow analyzing upto the relevant commit
-
- 07 Nov, 2018 4 commits
-
-
Stan Hu authored
-
Francisco Javier López authored
This new endpoint allow users to update a submodule's reference. The MR involves adding a new operation RPC operation in gitaly-proto (see gitlab-org/gitaly-proto!233) and change Gitaly to use this new version (see gitlab-org/gitaly!936). See gitlab-org/gitlab-ce!20949
-
Mark Chao authored
Suitable for testing old and new paths involved for each file in diff
-
Mark Chao authored
Suitable for testing old and new paths involved for each file in diff
-
- 05 Nov, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
This behaviour I removed in 08cdf65b, but this reverts this specific line. In case storages, or other options changes which are set by the Rails environment, this will easier to migrate to. Storage paths is kept in plural, to support multiple storage in later release for just testing purposes. But its probable that multi Gitaly scenarios need to be tested.
-
- 26 Oct, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
This behaviour I removed in 08cdf65b, but this reverts this specific line. In case storages, or other options changes which are set by the Rails environment, this will easier to migrate to. Storage paths is kept in plural, to support multiple storage in later release for just testing purposes. But its probable that multi Gitaly scenarios need to be tested.
-
- 24 Oct, 2018 2 commits
-
-
Zeger-Jan van de Weg authored
Rails requires a second storage for testing cross shard features. Gitaly will not boot if this second storage doesn't exist. So this will create this storage without adding it to the list of storages that Rails knows about.
-
Zeger-Jan van de Weg authored
Rails requires a second storage for testing cross shard features. Gitaly will not boot if this second storage doesn't exist. So this will create this storage without adding it to the list of storages that Rails knows about.
-
- 23 Oct, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
Broken storage used to be used to test situations where the Git storage wasn't being reached. These days we can just mock the Gitaly response. But given the broken storage is removed now, Gitaly can take over control of the storage being reachable. If it's not, Gitaly won't boot. That's nice for situations where a disk wasn't mounted for instance. Gitaly MR: https://gitlab.com/gitlab-org/gitaly/merge_requests/675
-
- 18 Oct, 2018 1 commit
-
-
Alessio Caiazza authored
GET :namespace/merge_requests/:id/ci_environments_status complexity already reached a limit for a direct serialization from an hash computed at within the controller function. Here we introduce a virtual model EnvironmentStatus and its serializer.
-
- 17 Sep, 2018 2 commits
-
-
Marcel Amirault authored
-
Marcel Amirault authored
-
- 12 Sep, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 06 Sep, 2018 2 commits
-
-
Bob Van Landuyt authored
In a file called `CODEOWNERS` in the root of a repository, in the `docs/`-folder or in the `.gitlab/` folder it is possible to define users that are 'owners' for specific code paths. A pattern can be defined on each line in the same way as it would in a `.gitignore` file. After that, one or more users can be specified using their username (using the `@username` format) or email address linked to their account. Comments can be preceded with a `#`. If a filename starts with `#` this can be escaped using `/#`. For example: # All files in the `docs/` directory should be reviewed by a # technical writer: docs/* @jane @joe # Ruby files should be reviewed by a backend maintainer: *.rb alice@development.gitlab.org The code owners will be displayed when viewing a blob, if a user for the username/email cannot be found, nothing will be shown. When multiple patterns match the blob being viewed, the last entry will be used.
-
Bob Van Landuyt authored
This ports the changes for the CODEOWNERS feature to CE: - It adds the CODEOWNERS file. - It adds the mention of the `with-codeowners` branch in TestEnv
-
- 12 Aug, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 07 Aug, 2018 3 commits
-
-
Winnie Hellmann authored
-
Rubén Dávila authored
Instead of invoking git commands from GitLab we are now invoking the `list_new_blobs` RPC from Gitaly that will return all the blobs found in the new revision that's being used for the push operation. With this change we're also fixing a bug by making push size checks only count the size of newly-pushed files
-
Rubén Dávila authored
-
- 31 Jul, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 10 Jul, 2018 1 commit
-
-
Sean McGivern authored
-
- 12 Jun, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 29 May, 2018 1 commit
-
-
blackst0ne authored
-
- 14 May, 2018 1 commit
-
-
- 25 Apr, 2018 2 commits
-
-
Zeger-Jan van de Weg authored
Picked from CE, from: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18364 But includes the EE changes too. Among the required changes are dropping of repository_storage_path from Geo tables. Geo stored `repository_storage_path` in four models, which initially was modeled after the interface of Gitlab::Shell rather than storing only the needed data. Given this inferred data had no place nor need to be stored I opted for deleting it.
-
Zeger-Jan van de Weg authored
Direct disk access is done through Gitaly now, so the legacy path was deprecated. This path was used in Gitlab::Shell however. This required the refactoring in this commit. Added is the removal of direct path access on the project model, as that lookup wasn't needed anymore is most cases. Closes https://gitlab.com/gitlab-org/gitaly/issues/1111
-
- 23 Apr, 2018 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-