An error occurred fetching the project authors.
- 04 May, 2017 1 commit
-
-
Ruben Davila authored
-
- 01 May, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 26 Apr, 2017 1 commit
-
-
Douwe Maan authored
-
- 19 Apr, 2017 1 commit
-
-
James Lopez authored
-
- 18 Apr, 2017 1 commit
-
-
Valery Sizov authored
-
- 11 Apr, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 09 Apr, 2017 1 commit
-
-
blackst0ne authored
-
- 06 Apr, 2017 5 commits
-
-
Timothy Andrew authored
1. Have `MigrateToGhostUser` be a service rather than a mixed-in module, to keep things explicit. Specs testing the behavior of this class are moved into a separate service spec file. 2. Add a `user.reported_abuse_reports` association to make the `migrate_abuse_reports` method more consistent with the other `migrate_` methods.
-
Timothy Andrew authored
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
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Markus Koller authored
-
- 30 Mar, 2017 1 commit
-
-
Fabio Huser authored
-
- 27 Mar, 2017 1 commit
-
-
George Andrinopoulos authored
-
- 24 Mar, 2017 1 commit
-
-
Alexander Randa authored
-
- 17 Mar, 2017 1 commit
-
-
Lin Jen-Shin authored
Hopefully this could fix: https://gitlab.com/gitlab-org/gitlab-ce/builds/12431186 To make sure that the email would never contain "joh" otherwise it would match to this `another_user`.
-
- 13 Mar, 2017 1 commit
-
-
George Andrinopoulos authored
-
- 09 Mar, 2017 1 commit
-
-
http://jneen.net/ authored
-
- 06 Mar, 2017 1 commit
-
-
Robert Speicher authored
-
- 05 Mar, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 28 Feb, 2017 1 commit
-
-
Douwe Maan authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 24 Feb, 2017 4 commits
-
-
Timothy Andrew authored
-
Timothy Andrew authored
Rather than using a separate `ghost` state. This lets us have the benefits of both ghost and blocked users (ghost: true, state: blocked) without having to rewrite a number of queries to include cases for `state: ghost`.
-
Timothy Andrew authored
1. Create a `Uniquify` class, which generalizes the process of generating unique strings, by accepting a function that defines what "uniqueness" means in a given context. 2. WIP: Make sure tests for `Namespace` pass, add more if necessary. 3. WIP: Add tests for `Uniquify`
-
Timothy Andrew authored
- "Associated" issues are issues the user has created + issues that the user is assigned to. - Issues that a user owns are transferred to a "Ghost User" (just a regular user with `state = 'ghost'` that is created when `User.ghost` is called). - Issues that a user is assigned to are moved to the "Unassigned" state. - Fix a spec failure in `profile_spec` — a spec was asserting that when a user is deleted, `User.count` decreases by 1. After this change, deleting a user creates (potentially) a ghost user, causing `User.count` not to change. The spec has been updated to look for the relevant user in the assertion.
-
- 23 Feb, 2017 5 commits
-
-
Douwe Maan authored
This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9. # Conflicts: # .rubocop.yml # .rubocop_todo.yml # lib/gitlab/ci/config/entry/global.rb # lib/gitlab/ci/config/entry/jobs.rb # spec/lib/gitlab/ci/config/entry/factory_spec.rb # spec/lib/gitlab/ci/config/entry/global_spec.rb # spec/lib/gitlab/ci/config/entry/job_spec.rb # spec/lib/gitlab/ci/status/build/factory_spec.rb # spec/lib/gitlab/incoming_email_spec.rb
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 15 Feb, 2017 2 commits
-
-
Annabel Dunstone Gray authored
-
Annabel Dunstone Gray authored
-
- 13 Feb, 2017 1 commit
-
-
Pawel Chojnacki authored
-
- 08 Feb, 2017 1 commit
-
-
Reza Mohammadi authored
Fixes #25279
-
- 06 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 05 Feb, 2017 1 commit
-
-
- 01 Feb, 2017 1 commit
-
-
Robert Speicher authored
-
- 26 Jan, 2017 1 commit
-
-
Robert Speicher authored
-
- 25 Jan, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-