gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2017-05-05	Multiple issue assignee: fix for CE restrictions	Valery Sizov

2017-05-05	Multiple issue assignee: CE restriction for multiple assignees	Valery Sizov

2017-05-04	Backport of multiple_assignees_feature [ci skip]	Valery Sizov

2017-04-06	Refactor resolvability checks based on type	Douwe Maan

2017-04-06	Make issue-from-discussion description text more consistent	Douwe Maan

2017-03-29	Create todos only for new mentions	Jarka Kadlecova

2017-03-13	Move `ResolveDiscussions` into `concerns/issues` folder	Bob Van Landuyt

2017-03-13	Update copy	Bob Van Landuyt
	One comments on something, not in something
2017-03-13	Rename variable	Bob Van Landuyt
	merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of
2017-03-13	Make sure the for a merge request only gets executed once.	Bob Van Landuyt

2017-03-13	Clean up `discussions_to_resolve`-method	Bob Van Landuyt

2017-03-13	Move `resolve_discussions_with_issue` to `Issues::CreateService`	Bob Van Landuyt

2017-03-13	Don't filter params and merge them back in later	Bob Van Landuyt
	By building the issue before filtering
2017-03-13	Correctly indent quotes in new issue description	Bob Van Landuyt
	By using `>`-quote style instead of `>>>`. Also: Update documentation images.
2017-03-13	Better variable names	Bob Van Landuyt
	So the title doesn't seem to be set _on_ a merge request.
2017-03-13	Optimize finding `discussions_to_resolve`	Bob Van Landuyt

2017-03-13	Link 'discussion' instead of date	Bob Van Landuyt
	Since the date would be wrong for people in different timezones.
2017-03-13	Move functionality for resolving discussions into a concern	Bob Van Landuyt

2017-03-13	Always require MR-iid for resolving discussions	Bob Van Landuyt
	And deduplicate the finding of MR's & discussions. Now the searching is done in the service, istead of the controller & the API.
2017-03-13	Delegate a single discussion to a new issue	Bob Van Landuyt
	Delegate a discussion in a merge request into a new issue. The discussion wil be marked as resolved and a system note will be added linking to the newly created issue.
2017-03-07	Address review comments	Valery Sizov

2017-03-03	Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into orderable-issues	Valery Sizov

2017-03-02	Address review comments	Valery Sizov

2017-03-01	Enable and autocorrect the CustomErrorClass cop	Sean McGivern

2017-02-28	[Issue Board Sorting] Set position for newly created issues	Valery Sizov

2017-02-24	Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into orderable-issues	Valery Sizov

2017-02-21	Spam check and reCAPTCHA improvements	Oswaldo Ferreira

2017-02-17	Frontend updates to positioning the issue in lists	Phil Hughes

2017-02-17	Allow issues in boards to be ordered	Douwe Maan

2017-02-13	Use safe navigation operator to make rubocop happy	winniehell

2017-02-12	fix issue creation from milestone doesn't assign the milestone	wendy0402

2017-02-07	Use reCaptcha when an issue identified as spam	Jarka Kadlecova

2016-12-28	Check if user can read issue before being assigned	Felipe Artur

2016-12-16	Enable Style/MultilineOperationIndentation in Rubocop, fixes #25741	Rydkin Maxim

2016-12-05	Feature: delegate all open discussions to Issue	Bob Van Landuyt
	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.
2016-12-01	Refactor JiraService by moving code out of JiraService#execute method	Adam Niedzielski
	The implicit interface of project services states that the "execute" method is meant to be called when project hooks are executed. Currently JiraService does not support any project events even though JiraService#supported_events says that "commit" and "merge_request" are supported. They are only used to render correct options in JIRA configuration screen, but they are not supported. Because of that, this commit makes "execute" method a no-op.
2016-11-07	Process commits in a separate worker	Yorick Peterse
	This moves the code used for processing commits from GitPushService to its own Sidekiq worker: ProcessCommitWorker. Using a Sidekiq worker allows us to process multiple commits in parallel. This in turn will lead to issues being closed faster and cross references being created faster. Furthermore by isolating this code into a separate class it's easier to test and maintain the code. The new worker also ensures it can efficiently check which issues can be closed, without having to run numerous SQL queries for every issue.
2016-10-19	Include global labels when moving an issue to another project	Douglas Barbosa Alexandre

2016-09-08	Add bulk update support for merge requests list	Dmitriy Zaporozhets
	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-09-01	Scope hooks thal will run for confidential issues	Douglas Barbosa Alexandre

2016-09-01	Fix confidential issues should not be passed to Webhooks	Douglas Barbosa Alexandre

2016-08-19	Merge branch '4273-slash-commands' into 'master'	Robert Speicher
	Support slash commands in issues / MR description & comments See merge request !5021
2016-08-18	Fix specs and implement fixes based on failing specs	Douwe Maan

2016-08-17	Merge branch '2451-fix-mentions-in-issue-updates' into 'master'	Robert Speicher
	Send notification emails when users are newly mentioned in issue or MR edits ## What does this MR do? Introduces "new mention in issue" and "new mention in MR" email notifications. Editing a Mentionable title or description and adding a mention to a user who was not previously mentioned will now send them a notification email, following usual permissions for doing so. ## Why was this MR needed? Issues & MRs may be edited to include mentions to new people. We don't currently send out email notifications of these edits to anyone, although they do create TODOs. This brings email notifications into parity with TODOs. ## What are the relevant issue numbers? Closes #2451 See merge request !5800
2016-08-17	Merge branch 'master' into 4273-slash-commands	Douwe Maan
	# Conflicts: # app/services/issues/create_service.rb
2016-08-16	Further refactor and syntax fixes.	Patricio Cano

2016-08-15	Refactored AkismetHelper into AkismetService and cleaned up `Spammable`	Patricio Cano
	- Refactored SpamCheckService into SpamService
2016-08-15	Refactored spam related code even further	Patricio Cano
	- 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
2016-08-15	Complete refactor of the `Spammable` concern and tests:	Patricio Cano
	- Merged `AkismetSubmittable` into `Spammable` - Clean up `SpamCheckService` - Added tests for `Spammable` - Added submit (ham or spam) options to `AkismetHelper`
2016-08-15	Lay the ground works to submit information to Akismet	Patricio Cano
	- 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.