- Aug 08, 2015
-
-
Douwe Maan authored
-
Douwe Maan authored
# Conflicts: # app/views/projects/merge_requests/_show.html.haml
-
- Aug 07, 2015
-
-
Stan Hu authored
-
- Aug 06, 2015
-
-
Gert Goet authored
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Douwe Maan authored
-
Stan Hu authored
Partial fix #2202
-
- Aug 05, 2015
-
-
Valery Sizov authored
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Stan Hu authored
Closes #2116 Closes https://github.com/gitlabhq/gitlabhq/issues/9502
-
- Aug 04, 2015
-
-
Kamil Trzcińśki authored
-
Zeger-Jan van de Weg authored
-
- Aug 02, 2015
- Jul 31, 2015
-
-
Kamil Trzcińśki authored
-
Douwe Maan authored
-
Stan Hu authored
HTML span elements only apply to a single line, and in the case of multi-line comments, the highlighting was dropped as a result. Ensure that each line has the proper styling to fix this. Closes #1577
-
- Jul 30, 2015
-
-
Robert Speicher authored
-
Stan Hu authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/9500
-
- Jul 29, 2015
-
-
Achilleas Pipinellis authored
-
Stan Hu authored
Add gitlab-shell to error message to give user a clue that something may be wrong there. Ran into this in #2082. User was told that repositories were created when they were not due to hooks symlink being wrong.
-
Jacob Vosmaer (GitLab) authored
-
Jacob Vosmaer (GitLab) authored
-
Douwe Maan authored
-
Valery Sizov authored
-
Daryl Chan authored
- Updated CHANGELOG
-
- Jul 28, 2015
-
-
Stan Hu authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- Jul 27, 2015
-
-
Hiroyuki Sato authored
-
- Jul 26, 2015
- Jul 24, 2015
-
-
Stan Hu authored
Steps to reproduce: 1. Create a project with a README 2. In the actual remote, type: `git symbolic-ref HEAD refs/heads/nowhere` 3. Check that HEAD is gone via `git ls-remote .` 4. Go to the projects page and see the Error 500 Closes https://github.com/gitlabhq/gitlabhq/issues/9484
-
Daniel Gerhardt authored
Starting with migration `20150717130904` commit count is stored in the database. For existing projects it defaults to `0` and is updated to the correct value when commits are pushed. The newly introduced rake task updates the commit count for all projects which have not been updated yet. Refs !986, !989, #2040.
-