Handle LDAP missing credentials error with a flash message.
If a user fails to provide a username or password to the LDAP login form then a 500 error is returned due to an exception being raised in omniauth-ldap. This gem has been amended to use the omniauth error propagation function (fail!) to pass this exception message to the registered omniauth failure handler so that the Rails application can handle it approriately. The failure function now knows about standard exceptions and no longer requires a specific check for the OmniAuth::Error exception added by commit f322975. This resolves issue #1077. Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
Create the githost.log file if necessary.
This resolves issue #1121. Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
Updated merge request subheading.
Changed "authored or assigned to you" to read "authored by or assigned to you" which reads better.
Merge pull request #1122 from patthoyts/pt/missing-log
Create the githost.log file if necessary.
Merge pull request #1118 from patthoyts/pt/ldap-missing-password
Handle LDAP missing credentials error with a flash message.
Merge pull request #1133 from robbytaylor/master
Updated merge request subheading.
Merge pull request #1127 from riyad/use-decorators
Use CommitDecorator more
Merge branch 'add_wiki_comments' of git://github.com/seeingidog/gitla…
…bhq into seeingidog-add_wiki_comments Conflicts: app/controllers/admin/mailer_controller.rb app/controllers/notes_controller.rb
* don't show pointer cursor for for the whole list item any more * fix hover color for links in .row_title
Add automatic HTML id attributes to markdown headings to allow linking
to content sections in wiki
Fixed dashboard loader, fixed 404 for reporter on empty wiki page.
Styled Wiki edit page
Modified the repo_dump and repo_restore rake tasks to properly du…
…mp and restore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).
Merge pull request #1129 from meskyanichi/master
Potential solution for current `rake gitlab:app:backup_restore` issues.
Post-receive hook should be owned by gitlab user, not git.
Merge pull request #1154 from meskyanichi/master
As per request: Post-receive hook should be owned by gitlab user, not git.
Merge pull request #1144 from riyad/break-up-links-with-nested-format…
…ing-rebased Break up links with nested formating (rebased)