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

Age	Commit message (Collapse)	Author
2017-08-18	Use `try` instead of `repond_to?` and a method call	Douwe Maan

2017-08-17	Prefer polymorphism over `is_a?`	Douwe Maan

2017-07-21	Expire ETag cache on note when award emoji changes	Sean McGivern

2017-06-21	Enable Style/DotPosition Rubocop :cop:	Grzegorz Bizon

2017-06-07	Added Cop to blacklist polymorphic associations	Yorick Peterse
	One should really use a separate table instead of using polymorphic associations. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11168 for more information.
2017-04-06	Move a user's award emoji to the ghost user	Timothy Andrew
	... when the user is destroyed. 1. Normally, for a given awardable and award emoji name, a user is only allowed to create a single award emoji. 2. This validation needs to be removed for ghost users, since: - User A and User B have created award emoji - with the same name and against the same awardable - User A is deleted. Their award emoji is moved to the ghost user - User B is deleted. Their award emoji needs to be moved to the ghost user. However, this breaks the uniqueness validation, since the ghost user is only allowed to have one award emoji of a given name for a given awardable
2017-02-09	Gather issuable metadata to avoid n+ queries on index view	Felipe Artur

2016-06-29	Add emoji.rb in lib/gitlab instead of using the gitlab_emoji gem.	Connor Shea
	No reason to split it into a separate gem when the gem barely did anything. We can use gemojione directly, making updating gemojione that much easier. Also fix the Rake task and update gemojione to 2.6.1. This adds the EmojiOne Spring update. Changelog: https://github.com/jonathanwiesel/gemojione/blob/master/CHANGELOG.md
2016-05-18	Fix latests concerns	ZJ van de Weg

2016-05-06	Create table for award emoji	Zeger-Jan van de Weg