An error occurred fetching the project authors.
- 24 Feb, 2017 1 commit
-
-
Felipe Artur authored
-
- 23 Feb, 2017 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 09 Feb, 2017 1 commit
-
-
Felipe Artur authored
-
- 07 Feb, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 25 Jan, 2017 1 commit
-
-
Robert Speicher authored
-
- 15 Jan, 2017 1 commit
-
-
Ruben Davila authored
-
- 23 Dec, 2016 1 commit
-
-
Tiago Botelho authored
-
- 21 Dec, 2016 1 commit
-
-
Tiago Botelho authored
-
- 05 Dec, 2016 1 commit
-
-
Bob Van Landuyt authored
When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue.
-
- 08 Sep, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 25 Aug, 2016 1 commit
-
- 15 Aug, 2016 5 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
- Refactored SpamCheckService into SpamService
-
Patricio Cano authored
- Added controller actions as reusable concerns - Added controller tests
-
Patricio Cano authored
- Removed unnecessary column from `SpamLog` - Moved creation of SpamLogs out of its own service and into SpamCheckService - Simplified code in SpamCheckService. - Moved move spam related code into Spammable concern
-
Patricio Cano authored
- New concern `AkismetSubmittable` to allow issues and other `Spammable` models to be submitted to Akismet. - New model `UserAgentDetail` to store information needed for Akismet. - Services needed for their creation and tests.
-
- 09 Aug, 2016 1 commit
-
-
tiagonbotelho authored
-
- 02 Aug, 2016 1 commit
-
-
Robert Speicher authored
Now we link to the standard `IssuesController#new` action, and let it redirect if we're using an external tracker.
-
- 01 Aug, 2016 1 commit
-
-
Robert Speicher authored
Prior, in order to display the correct link to "Issues" in the project navigation, we were performing a check against the project to see if it used an external issue tracker, and if so, we used that URL. This was inefficient. Now, we simply _always_ link to `namespace_project_issues_path`, and then in the controller we redirect to the external tracker if it's present. This also removes the need for the url_for_issue helper. Bonus!
-
- 26 Jul, 2016 1 commit
-
-
Patricio Cano authored
-
- 27 Jun, 2016 1 commit
-
-
Z.J. van de Weg authored
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 13 Jun, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 01 Jun, 2016 1 commit
-
-
Z.J. van de Weg authored
-
- 24 May, 2016 1 commit
-
-
Robert Speicher authored
Also removes the note from the development/testing.md guide
-
- 12 May, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 11 May, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 10 May, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 30 Apr, 2016 1 commit
-
-
Grzegorz Bizon authored
Closes #15533
-
- 21 Mar, 2016 2 commits
-
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
-
- 19 Mar, 2016 2 commits
-
-
Yorick Peterse authored
In the real world a project always has a repository. This fact allows code such as Issue#related_branches to work without explicitly checking if a repository exists.
-
Zeger-Jan van de Weg authored
-
- 17 Mar, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-