... 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

... when the user is destroyed.

To clarify, this regards abuse reports that the to-be-deleted user has _reported_.

Introduction
------------

1. The foreign key was not explicitly specified on the association.
2. The `AbuseReport` model contains two references to user - `reporter_id` and
   `user_id`
3. `user.abuse_report` is supposed to return the single abuse report where
   `user_id` refers to the given user.

Bug Description
---------------

1. `user.abuse_report` would return an abuse report where `reporter_id` referred
   to the current user, if such an abuse report was present.

2. This implies a slightly more serious bug as well:

   - Assume User A filed an abuse report against User B
   - We have an abuse report where `reporter_id` is User A and `user_id` is User B
   - If User A is updated (`user_a.block`, for example), the abuse report would
     also be updated, such that both `reporter_id` _and_ `user_id` point to User A.

Fix
---

Explicitly declare the foreign key `user_id` in the `has_one` declaration

... when the user is destroyed.

1. When the user is deleted.

2. Refactor out code relating to "migrating records to the ghost user" into a
   `MigrateToGhostUser` concern, which is tested using a shared example.

Don't use FFaker in factories, use sequences instead

Closes #29643

See merge request !10184

Ensure users have a short username otherwise a click event is triggered outside the search field

Closes #29241

See merge request !10411

Quiet pipeline emails

Closes #24845

See merge request !10333

Enable the `bullet_logger` setting; enable `raise` in test environment

Closes #30129

See merge request !10263

Log errors in UpdatePagesService

See merge request !10335

Signed-off-by: Rémy Coutable <remy@rymai.me>

Improve performance of GitHub importer

Closes #28183

See merge request !10273

Remove deprecated code from pipeline processing service

Closes #30052

See merge request !10266

Fix race condition in namespace directory creation

See merge request !10268

Add support for Gitaly calls over TCP connection

Closes gitaly#166

See merge request !10410

Add feature flags for enabling (Upload|Receive)Pack

Closes gitaly#168

See merge request !10341

Make file templates easy to use and discover

Closes #25332

See merge request !9782

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

FFaker can generate data that randomly break our test suite. This
simplifies our factories and use sequences which are more predictive.
Signed-off-by: Rémy Coutable <remy@rymai.me>

Enable Style/Proc cop for rubocop

See merge request !10382

Closes gitaly#166

Closes gitaly#168

#22303 fix mode representation git::tree ( in base 8 )

Closes #22303

See merge request !9780