An error occurred fetching the project authors.
- 28 Jun, 2016 2 commits
-
-
winniehell authored
-
James Lopez authored
-
- 27 Jun, 2016 9 commits
-
-
Ruben Davila authored
This fix avoids exposing the information from the wiki repository of other project.
-
Douwe Maan authored
-
Annabel Dunstone authored
-
Annabel Dunstone authored
-
Patricio Cano authored
-
winniehell authored
-
Connor Shea authored
Add max-height to prevent images from displaying larger than the provided screen size. Also fix a failing test and add a new one.
-
Connor Shea authored
-
Robert Schilling authored
-
- 26 Jun, 2016 1 commit
-
-
Robert Speicher authored
[ci skip]
-
- 25 Jun, 2016 2 commits
-
-
Simon Welsh authored
-
Simon Welsh authored
-
- 24 Jun, 2016 7 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
Rémy Coutable authored
Fix a wrong MR status when merge_when_build_succeeds & project.only_allow_merge_if_build_succeeds are true The issue was that `MergeRequest#mergeable?` returns false when the CI state is not success and project.only_allow_merge_if_build_succeeds is true. In this case `Projects::MergeRequestsController#merge` would return the `:failed` status when enabling `merge_when_build_succeeds`, thus leading to a weird state and the MR never automatically merged. The fix is to disable the CI state check in the controller safeguard that early return the `:failed` status. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Yorick Peterse authored
This is meant to go in 8.9.1, not 8.10.0. [ci skip]
-
DJ Mountney authored
The email check used in the Heath Check doesn't properly make use of enough of the SMTP config options to be able to properly test the STMP connection, and as a result could cause a failure. In order to fix it we have overwritten the email_configured? method in the health check so that it does not check email status during the standard health check.
-
Yorick Peterse authored
[ci skip]
-
James Lopez authored
Fix tmp file being deleted after the request plus some cleanup and improved erroring for this situation
-
- 23 Jun, 2016 15 commits
-
-
Connor Shea authored
-
Annabel Dunstone authored
-
Alfredo Sumaran authored
-
Alfredo Sumaran authored
-
Paco Guzman authored
-
Stan Hu authored
Closes #18690
-
Marc Siegfriedt authored
rely only on IssuesFinder docs and changelog
-
Alejandro Rodríguez authored
-
Nathan Bush authored
-
Steve Norman authored
-
Kamil Trzcinski authored
-
Sean McGivern authored
Postgres and MySQL don't guarantee that pagination with `LIMIT` and `OFFSET` will work if the ordering isn't unique. From the Postgres docs: > When using `LIMIT`, it is important to use an `ORDER BY` clause that > constrains the result rows into a unique order. Otherwise you will get > an unpredictable subset of the query's rows Before: [1] pry(main)> issues = 1.upto(Issue.count).map { |i| Issue.sort('priority').page(i).per(1).map(&:id) }.flatten [2] pry(main)> issues.count => 81 [3] pry(main)> issues.uniq.count => 42 After: [1] pry(main)> issues = 1.upto(Issue.count).map { |i| Issue.sort('priority').page(i).per(1).map(&:id) }.flatten [2] pry(main)> issues.count => 81 [3] pry(main)> issues.uniq.count => 81
-
James Lopez authored
-
Paco Guzman authored
-
Z.J. van de Weg authored
-
- 22 Jun, 2016 4 commits
-
-
Douglas Barbosa Alexandre authored
-
Connor Shea authored
-
Connor Shea authored
-
Rémy Coutable authored
[ci skip] Signed-off-by: Rémy Coutable <remy@rymai.me>
-