An error occurred fetching the project authors.
- 26 May, 2015 3 commits
- 25 May, 2015 9 commits
-
-
Sytse Sijbrandij authored
-
Sytse Sijbrandij authored
Document expanded autolinking in doc/markdown/markdown.md See merge request !706
-
Robert Speicher authored
-
Sytse Sijbrandij authored
-
Douwe Maan authored
Disable "New Issue" and "New Merge Request" buttons when features are disabled in project settings Closes #1676 See merge request !691
-
Stan Hu authored
Closes #1676
-
Robert Schilling authored
-
Robert Schilling authored
Remove redundant CHANGELOG entry This was moved into v7.10.4, but I forgot to delete it from the v7.11 list. See merge request !692
-
Douwe Maan authored
Add support for Webhook note events This MR adds support for note events (comments) for WebHooks. Perhaps the only potential source of confusion is that the settings indicates "Note Events" instead of "Comments". What do you think? Screenshot after: ![image](https://gitlab.com/stanhu/gitlab-ce/uploads/299b141d82f7b14943a74258d5c57ca6/image.png) Closes https://github.com/gitlabhq/gitlabhq/issues/6745 See merge request !673
-
- 22 May, 2015 11 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
Sytse Sijbrandij authored
-
Douwe Maan authored
Use the user list from the target project in a merge request ### What does this MR do? This MR derives the assignable users from the target project. ### Why was this MR needed? In a merge request, the assignable users uses the list from the forked project, not the target project where the merge request will be going. For example, if I fork a project from the gitlab-org namespace into my personal namespace, make some changes, and then create a merge request, the only users I see are me. I think it makes more sense to show all the users in gitlab-org. This is a regression caused by 1c2711f7. ### What are the relevant issue numbers? Closes #1535 See merge request !682
-
Job van der Voort authored
-
Stan Hu authored
-
Stan Hu authored
Closes #1535
-
Job van der Voort authored
-
Dmitriy Zaporozhets authored
-
Job van der Voort authored
Changing your time zone Added doc and link in workflow to how to change your time zone in Gitlab. I used the following documents as reference. Please double check that the instructions I wrote are correct. http://www.borngeek.com/2015/02/27/setting-the-time-zone-in-gitlab/ https://gitlab.com/gitlab-org/gitlab-ce/issues/443 I found that several users have this same issue, that they don't know how to change their time zone: https://github.com/gitlabhq/gitlabhq/issues/5555 https://gitlab.com/gitlab-org/omnibus-gitlab/issues/347 https://gitlab.com/gitlab-org/gitlab-ce/issues/56 http://jonathonreinhart.blogspot.com/2014/10/gitlab-time-zone-issues.html http://stackoverflow.com/questions/5073917/why-doesnt-config-time-zone-seem-to-do-anything See merge request !1827
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/6745
-
- 21 May, 2015 17 commits
-
-
Karen Carias authored
-
Karen Carias authored
-
Douwe Maan authored
Fix Atom feeds. Fixes #1643 and #1644. See merge request !688
-
Douwe Maan authored
-
Douwe Maan authored
Work around a Chrome 43 bug preventing note editing Fixes #1568 - and I mean "fixes" I have no idea what causes this or why this fixes it and can't dig into it further right now, but the bug seems like a blocker so this needs to be fixed for 7.11. See merge request !684
-
Douwe Maan authored
-
Job van der Voort authored
-
Job van der Voort authored
-
Hannes Rosenögger authored
Update CHANGELOG with v7.10.4 changes See merge request !662
-
Douwe Maan authored
Updated the gitlab_git gem
-
Jeroen van Baarsen authored
Moved changelog stuff to the correct release
-
Jeroen van Baarsen authored
**Why was this needed?** The changes are pulled in 7.12.0 but where mistakenly put under 7.11.0 [skip-ci] Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
Jeroen van Baarsen authored
Disabled expansion of top/bottom blobs for new file diffs
-
Jeroen van Baarsen authored
**What does this do?** It updated the version of gitlab_git to the latest version **Why is this needed?* There was a bug in rugged (dependency of gitlab_git) that causes a segfault error when seeding the database. That error has been fixed and the fix is in the latest version of gitlab_git Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
Alex Connor authored
-
Dmitriy Zaporozhets authored
Customize the sanitization whitelist only once Fixes #1651 See merge request !687
-
Robert Speicher authored
Fixes #1651
-