Handle nil restricted visibility settings
Return `true` from `non_restricted_level?` when the `restricted_visibility_levels` setting is nil. This addresses #2154.
cc @sytse
See merge request !1724
Api: sort merge_request comments
Add default_scope { order(created_at: :asc, id: :asc) } in Note so comments are sorted when fetched through api.
See merge request !256
Extend commit calendar to actually show what commits were made on a date
## What does this MR do?
This MR extends the commit calendar so it acutally shows what commits were made on a date and in which project.
It is based on the optimizations @dzaporozhets made for the calendar.
## Are there points in the code the reviewer needs to double check?
The UI and how the links are generated i guess. That feels hacky at the moment :/
## Screenshot:
I assume that i have to refactor this a bit more to make it a cleaner implementation, so please give me feedback on what needs to be changed :)
See merge request !326
Enable line wrapping per default.
This MR enables line wrapping by default and removes the checkbox to toggle it.
Let's be honest, noone likes horizontal scrollbars.
/cc @dzaporozhets @DouweM As discussed yesterday. Please take a look. Did I miss something?
The change feels to easy 😄
See merge request !396
Add support for external wikis
## What does this MR do?
This MR adds the possibility to replace the link to the internal wiki of gitlab with a custom link.
Currently this is realised as a service.
## What Use Case does this MR solve?
In my Company we already have a wiki System (Confluence).
We have a policy to use the existing wiki, so we can't switch to the internal wiki Gitlab provides.
This currently only leaves us two choices:
1. Disable the gitlab wiki. That means we completly loose the connection between wiki and code from the gitlab ui.
2. Create a simple wiki page with a link to our external wiki and hope that no one uses the internal one.
Both solutions are not really good.
So what can be done to improve the situation while making it as easy as possible for new developers to access both, wiki and gitlab?
Replacing the wiki link kinda like the JIRA integration replaces the issues link looks like a good first step to me. :)
This can probably be extended later to completly prevent access to the internal wiki (currently that's still possible if you know the link) or maybe to check if the link really points to a wiki.
## Screenshot:
See merge request !291
Douwe Maan
Marin Jankovski
Marin Jankovski
Jeroen van Baarsen
Vinnie Okada
Dmitriy Zaporozhets
Dmitriy Zaporozhets
Samuel Bernard
Hannes Rosenögger
Valery Sizov
