- 10 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
Instead of flushing the behind/ahead counts for all branches upon every push we now only flush the cache of branches that actually need to have these statistics recalculated. There are now basically 2 scenarios and their effects: 1. A user pushes a commit to the default branch, this results in the cache being flushed for all branches. 2. A user pushes to a non default branch, this results in _only_ the cache for that branch being flushed. The existing code (Repository#expire_cache) remains backwards compatible with the previous behaviour, the new behaviour is only applied when a branch name is passed as an argument. This ensures that when for example a project is deleted the cache for all branches is flushed.
-
- 08 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This caches the output of the following methods: * Repository#empty? * Repository#has_visible_content? * Repository#root_ref The cache for Repository#has_visible_content? is flushed whenever a commit is pushed to a new branch or an existing branch is removed. The cache for Repository#root_ref is only flushed whenever a user changes the default branch of a project. The cache for Repository#empty? is never explicitly flushed as there's no need for it.
-
- 12 12月, 2015 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 19 11月, 2015 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 13 11月, 2015 1 次提交
-
-
由 Kamil Trzcinski 提交于
- Enable CI by default for all new projects
-
- 18 10月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Stan Hu 提交于
If a branch is deleted with an open merge request, amended offline, and then pushed again, GitLab doesn't bother to update the merge request even though the last commit ID and/or code may have changed. This MR ensures that each push will update any relevant merge requests and adds a system note if this happens as well. Closes #2926
-
- 12 10月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 02 10月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 23 9月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 22 8月, 2015 1 次提交
-
-
由 Maël Valais 提交于
I also revamped the tests on "closing reference commits" (= "Fixes #xxxx" for example). Now, there are two different contexts: - when the commits with "closing reference" are pushed to the default branch, - when the commits with "closing reference" are pushed to a non-default branch. Closes gitlab-org/gitlab-ce#2190.
-
- 11 8月, 2015 3 次提交
-
-
由 Dmitriy Zaporozhets 提交于
This reverts commit 5daf44b7, reversing changes made to 2f706fbd.
-
由 Dmitriy Zaporozhets 提交于
This reverts commit 435f680b.
-
由 Dmitriy Zaporozhets 提交于
This reverts commit 957e849f, reversing changes made to 6b9dbe9f. Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 7月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 15 7月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 22 6月, 2015 1 次提交
-
-
由 Robert Speicher 提交于
-
- 12 6月, 2015 1 次提交
-
-
由 Stan Hu 提交于
Closes #1700 Closes #1720
-
- 02 6月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 06 5月, 2015 1 次提交
-
-
由 Stan Hu 提交于
In an empty repository, pushing a new branch not called "master" would leave HEAD in an unknown state, causing ambiguity if another branch were pushed. This could in turn cause a new protected branch to be created and cause the default branch to change. * Closes #1561 * Closes #1576 * Closes https://github.com/gitlabhq/gitlabhq/issues/8883
-
- 24 4月, 2015 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 02 4月, 2015 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 21 3月, 2015 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 19 3月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 14 3月, 2015 2 次提交
-
-
由 Hannes Rosenögger 提交于
This reverts commit 07f9a3f9, reversing changes made to 48036751. Reverted this because the data is used in hooks as well.
-
由 Elliot 提交于
Remove unnecessary fetch of commit messages for initial push. This will reduce the memory usage significantly.
-
- 13 3月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 10 3月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 09 3月, 2015 1 次提交
-
-
由 Hannes Rosenögger 提交于
This commit disables process_commit_messages() for the initial push to the default branch. This fixes the mass SQL statements (~500000) that were executed during the initial push of the linux kernel for example.
-
- 03 3月, 2015 1 次提交
-
-
由 Stan Hu 提交于
1) Adds a DB migration for all services to toggle on push, issue, and merge events. 2) Upon an issue or merge request event, fire service hooks. 3) Slack service supports custom messages for each of these events. Other services not supported at the moment. 4) Label merge request hooks with their corresponding actions.
-
- 13 2月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 26 1月, 2015 2 次提交
-
-
由 Marco Wessel 提交于
-
由 Marco Wessel 提交于
-
- 12 1月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Also execute GitLab CI on creating tag via UI
-
- 29 12月, 2014 1 次提交
-
-
由 Ciro Santilli 提交于
and more readable.
-
- 12 11月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-