- 06 7月, 2018 1 次提交
-
-
由 Jacob Vosmaer 提交于
This partially reverts commit 64dfe2cb.
-
- 05 7月, 2018 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
This reverts merge request !20339
-
- 04 7月, 2018 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 28 6月, 2018 2 次提交
-
-
-
由 Zeger-Jan van de Weg 提交于
Prior to this change, most the commits counted were done through Gitaly. This removes the last point where this wasn't the case. This makes the `rugged_count_commits` method obsolete, with its tests. Closes https://gitlab.com/gitlab-org/gitaly/issues/315
-
- 27 6月, 2018 2 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
- 26 6月, 2018 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 22 6月, 2018 1 次提交
-
-
- 06 6月, 2018 2 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Zeger-Jan van de Weg 提交于
Gitaly itself hold very little state, other than the data on disk. This limits the interfaces to set feature flags. Gitaly now has the ability to interpret the request metadata to check for feature flags. https://gitlab.com/gitlab-org/gitaly/merge_requests/704 This allows clients control on the Gitaly server, and given that Rails has an internal chatops interface to set these values this was chosen as solution. Known limitation right now, is that this package doesn't support the opt out that other Gitaly features do.
-
- 19 5月, 2018 1 次提交
-
-
由 Ahmad Sherif 提交于
-
- 16 5月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Prior to this change, this was done through unicorn. In theory this could time out. Workhorse has been sending these raw patches and diffs for a long time and is stable in doing so. Added bonus is the fact that `Commit#to_patch` can be removed. `Commit#to_diff` too, which closes https://gitlab.com/gitlab-org/gitaly/issues/324 Closes https://gitlab.com/gitlab-org/gitaly/issues/1196
-
- 17 4月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
The execution path wasn't clear from the error, but either way this is a fix. Closes gitlab-org/gitaly#1115
-
- 04 4月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Acceptence testing was successfull in [#844](https://gitlab.com/gitlab-org/gitaly/issues/844) Part of gitlab-org/gitaly#670
-
- 07 3月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Part of gitlab-org/gitaly#324
-
- 02 3月, 2018 1 次提交
-
-
由 Ahmad Sherif 提交于
Closes gitaly#1046
-
- 19 2月, 2018 1 次提交
-
-
由 Sean McGivern 提交于
The tracking issue if this causes problems is https://gitlab.com/gitlab-org/gitaly/issues/1028
-
- 17 2月, 2018 2 次提交
-
-
由 Micaël Bergeron 提交于
# modified: lib/gitlab/git/commit.rb
-
由 Micaël Bergeron 提交于
-
- 07 2月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
The refs hash is used to determine what branches and tags have a commit as head in the network graph. The previous implementation depended on Rugged#references. The problem with this implementation was that it depended on rugged, but also that it iterated over all references and thus loading more data than needed if for example the project uses CI/CD environments, Pipelines, or Merge Requests. Given only refs are checked the network cares about the GraphHelper#refs method has no need to reject those, simplifying the method. Closes gitlab-org/gitaly#880
-
- 18 1月, 2018 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 15 1月, 2018 1 次提交
-
-
由 Ahmad Sherif 提交于
Closes gitaly#915
-
- 05 1月, 2018 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 19 12月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Uses `list_commits_by_oid` on the CommitService, to request the needed commits for pipelines. These commits are needed to display the user that created the commit and the commit title. This includes fixes for tests failing that depended on the commit being `nil`. However, now these are batch loaded, this doesn't happen anymore and the commits are an instance of BatchLoader.
-
- 07 12月, 2017 1 次提交
-
-
由 micael.bergeron 提交于
-
- 05 12月, 2017 2 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
- Added tests for Git::Commit.shas_with_signatures
-
由 Ahmad Sherif 提交于
Closes gitaly#737
-
- 01 11月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 27 10月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Now, when requesting a commit from the Repository model, the results are not cached. This means we're fetching the same commit by oid multiple times during the same request. To prevent us from doing this, we now cache results. Caching is done only based on object id (aka SHA). Given we cache on the Repository model, results are scoped to the associated project, eventhough the change of two repositories having the same oids for different commits is small.
-
- 20 9月, 2017 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 12 9月, 2017 1 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
- 23 8月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 17 8月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 08 8月, 2017 4 次提交
-
-
由 Brian Neel 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
This helps keep the abstraction layers simpler, and also keep the interface of those methods consistent, in case of implementation changes.
-
由 Alejandro Rodríguez 提交于
-
- 03 8月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 27 7月, 2017 1 次提交
-
-
由 Alexis Reigel 提交于
the rugged versions up to 0.26.0b3 had a bug concerning the signature extraction. The extracted signature was not always the same, probably due to a buffer (overflow) issue in libgit. see https://github.com/libgit2/rugged/issues/608
-