- 24 Jul, 2016 5 commits
-
-
Stan Hu authored
-
Stan Hu authored
-
Stan Hu authored
Closes gitlab-com/support-forum#874
-
Achilleas Pipinellis authored
Add links to the real markdown.md file for all GFM examples ## What does this MR do? Add links to the real markdown.md file for all GFM examples since they will not render correctly on docs.gitlab.com. We already have a note https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440, but better be explicit. See merge request !5458
-
Achilleas Pipinellis authored
-
- 23 Jul, 2016 8 commits
-
-
Stan Hu authored
Fix bug where replies to commit notes displayed in the MR discussion tab wouldn'… Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/20157 See merge request !5446
-
Douwe Maan authored
Add gitlab-workhorse version to admin dashboard ## What does this MR do? Add gitlab-workhorse version to admin dashboard. ## What are the relevant issue numbers? Closes #15418 ## Screenshot ![Zrzut_ekranu_2016-07-20_o_23.20.55](/uploads/ba6761e2145d903ac87bc7198bc8b182/Zrzut_ekranu_2016-07-20_o_23.20.55.png) ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - Tests - [x] Add test - show Gitlab Workhorse version on Admin Dashboard - [x] All builds are passing - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) cc @ubudzisz @yorickpeterse @grzesiek [@chastell](https://github.com/chastell) [@tomash](https://github.com/tomash) See merge request !5321
-
Douwe Maan authored
Fix bug where replies to commit notes displayed in the MR discussion tab wouldn't show up on the commit page
-
Robert Speicher authored
Improve project rename log messages for better debugging This should help diagnose issues such as #20178. See merge request !5450
-
Dmitriy Zaporozhets authored
Add light border to rounded avatars Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/20128 To make it clear that avatar is cropped by border radius cc @hazelyang See merge request !5429
-
Stan Hu authored
Helping to diagnose #20178
-
Katarzyna Kobierska authored
-
Katarzyna Kobierska authored
Test for showing GitLab Workhorse version on Admin Dashboard Refactoring
-
- 22 Jul, 2016 27 commits
-
-
Douwe Maan authored
Add note to say GFM doesn't work on documentation website See merge request !5440
-
Douwe Maan authored
-
Robert Speicher authored
Fix missing repo_ref param Closes #19444 See merge request !5435
-
Douwe Maan authored
Load project invited groups and members eagerly in ProjectTeam#fetch_members ## What does this MR do? Load project invited groups and members eagerly in `ProjectTeam#fetch_members`, reducing number of queries to DB. ## Are there points in the code the reviewer needs to double check? N/A ## Why was this MR needed? `ProjectTeam#fetch_members` is part of the code path of `Participable#raw_participants`, so it should improve its performance a bit. ## What are the relevant issue numbers? #19985 ## Screenshots (if relevant) N/A ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - ~~[ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~ - ~~[ ] API support added~~ - ~~Tests~~ - ~~[ ] Added for this feature/bug~~ - ~~[ ] All builds are passing~~ - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5436
-
Douwe Maan authored
Gracefully handle case when keep-around references are corrupted or exist already 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 does not allow you to delete or re-create a reference that has been corrupted, even with the force parameter. A truncated reference will stay that way until manual intervention. Closes #20109 See merge request !5430
-
Achilleas Pipinellis authored
Add detailed info on storage path mountpoints Users that run GitLab from source should be extra careful when using the multiple repository storage feature. Make sure there is a detailed explanation why this happens and how to overcome it. See merge request !5437
-
Achilleas Pipinellis authored
[ci skip]
-
Ahmad Sherif authored
-
barthc authored
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Stan Hu authored
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
-
Rémy Coutable authored
Make Notify specs more robust by setting up assignee names Closes #20121. See merge request !5427
-
Achilleas Pipinellis authored
Refactor repository storages documentation Use detailed information on using the multiple repository storage feature See merge request !5428
-
Achilleas Pipinellis authored
[ci skip]
-
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>
-
Achilleas Pipinellis authored
Merge branch '20107-update-documentation-according-to-the-new-multiple-repository-storage-paths-feature' into 'master' Update documentation according to the new multiple git mount points feature Closes #20107 See merge request !5411
-
Achilleas Pipinellis authored
Refactor Slack service documentation See merge request !5421
-
Achilleas Pipinellis authored
[ci skip]
-
Achilleas Pipinellis authored
Move admin application settings to own path Move existing documentation to its own `user/admin_area/settings` path. See merge request !5420
-
Achilleas Pipinellis authored
Refactor protected branches documentation Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/19832 See merge request !5419
-
Achilleas Pipinellis authored
[ci skip]
-
Achilleas Pipinellis authored
-
Rémy Coutable authored
Simpler two queries than one JOIN with subquery This is a follow up from !5347 Originally it was: ``` ruby pipeline = pipelines.latest_successful_for(ref) builds.where(pipeline: pipeline).latest.with_artifacts ``` However MySQL would complain that we can't use `IN` against a subquery which has `LIMIT`. Using `INNER JOIN` would be a workaround, however, doing that is too complicated in current version of Rails. So let's just use two queries in this case. Closes #14419 See merge request !5388
-
Achilleas Pipinellis authored
-
Achilleas Pipinellis authored
Explain CI_PROJECT_NAMESPACE better ## What does this MR do? Explain CI_PROJECT_NAMESPACE better by adding "The project namespace (username or groupname) that is currently being built". ## Are there points in the code the reviewer needs to double check? Are `username` and `groupname` known words? We use it [here](http://docs.gitlab.com/ee/api/namespaces.html). ## Why was this MR needed? Because `namespace` isn't a well known term. ## What are the relevant issue numbers? ## Screenshots (if relevant) See merge request !5407
-
Stan Hu authored
Add a spec for #20079 - This MR adds a spec for the fix for #20079 that was implemented in !5400. - The spec is going in separately, just so the fix could go in as soon as possible. See merge request !5414
-