First entry in wiki history leads to newest revision.

Scroll below the navbar

Fixes #1866

Show the markdown anchors by scrolling below the fixed top navbar.

See merge request !1390

Git HTTP blacklist

See merge request !1328

Add Changelog Guidelines to monthly.md

Fixes #1868

Added the changelog guidelines according to the issue mentioned above. @sytse I didn't add the extra lines to the 7.7.0 log, since we have a codefreeze soon.

/cc @job

See merge request !1389

Added DISCLAIMER to CHANGELOG

 ForbiddenAction constant name fix

See merge request !1387

Refactor push data builder

See merge request !1384

Mr widget remove source branch checkbox

Fixes #1858

Renamed custom `checkbox` css class for remove source branch checkbox because it was being overwritten on Safari by `checkbox` from bootstrap in `_forms.scss`

After rename, alignment looks corrected

See merge request !1386

Add search option to project api

When using Ajax to search for users authorised projects we need to do a search query on the returned list rather than doing a request using `/search/:query` option.

This MR also adds a simple spec for project ordering feature that got added in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/266 but no specs were provided.

See merge request !1385

Rename the checkbox css class to prevent it from being overwritten by the same named bootstrap class.

Also execute GitLab CI on creating tag via UI

When push tag - trigger GitLab CI

See merge request !1383

Fix File blame not respecting branch selection

See merge request !1382

Flatten the directory hierarchy while there is only one directory descendant

In some languages, especially java, the directory structure reflects the package structure.This means that using the file tree browser to reach the directories that matter you have to click a lot of directories containing only another subdirectory.

This merge request tries to enhance this by showing and providing the link to the first directory that doesn't contain only one directory.

See also [this feature request](http://feedback.gitlab.com/forums/176466-general/suggestions/6236769-jump-forward-to-the-first-folder-that-has-more-tha)

This is very similar to what [GitHub does](https://github.com/blog/1877-folder-jumping), but I don't think graying out the empty directories is really necessary.

Screenshots: [Before](https://gitlab.com/uploads/marmis85/gitlab-ce/b683a0000f/before.png) - [After](https://gitlab.com/uploads/marmis85/gitlab-ce/a23725a1c1/after.png)

I'm actually very new at ruby, rails, haml, and almost everything involved in Gitlab's development...
From what I could understand, when we render each directory item in the list we only have the data structure representing the item but not his descendants.
To iterate through the hierarchy I call Gitlab::Git:Tree.where() but I'm not sure if this is the most efficient way.

I also considered making every directory a clickable link, but I tried that and in the end it wasn't very useful and reduced the click target for the most useful directory.

See merge request !275

Release doc

See merge request !1381

Refactor release doc

* Follow issue as todo list instead of document
* move huge rc1 block to separate file
* cleanup and fix order of some actions

See merge request !1379

Easy dev install

@jeroenvanbaarsen  just tried the following:

1. Removing therubyracer from gemfile
2. Install node (brew install node or sudo apt-get install nodejs)
3. Run $ spinach features/

All worked as before, so this would mean people have to install the node dependency on their local machine, but in my experience this is much easier than installing libv8, especially for non ruby-devs. /cc @jacobvosmaer

See merge request !262

Async satellites

Do merge request automerge via satellite.

See merge request !1380