An error occurred fetching the project authors.
- 05 Nov, 2018 1 commit
-
-
Felipe Artur authored
-
- 23 Oct, 2018 2 commits
-
-
Jan Provaznik authored
It's possible that user pastes accidentally also unsubscribe link which is included in footer of notification emails. This unsubscribe link contains personal token which attacker then use to act as the original user (e.g. for sending comments under his/her identity).
-
Oswaldo Ferreira authored
-
- 06 Oct, 2018 1 commit
-
-
Stan Hu authored
This resolves a conflict and inconsistency with the EE version of app/models/note.rb.
-
- 02 Oct, 2018 1 commit
-
-
Brett Walker authored
-
- 17 Sep, 2018 1 commit
-
-
Yorick Peterse authored
This commit adds the module `FromUnion`, which provides the class method `from_union`. This simplifies the process of selecting data from the result of a UNION, and reduces the likelihood of making mistakes. As a result, instead of this: union = Gitlab::SQL::Union.new([foo, bar]) Foo.from("(#{union.to_sql}) #{Foo.table_name}") We can now write this instead: Foo.from_union([foo, bar]) This commit also includes some changes to make this new setup work properly. For example, a bug in Rails 4 (https://github.com/rails/rails/issues/24193) would break the use of `from("sub-query-here").includes(:relation)` in certain cases. There was also a CI query which appeared to repeat a lot of conditions from an outer query on an inner query, which isn't necessary. Finally, we include a RuboCop cop to ensure developers use this new module, instead of using Gitlab::SQL::Union directly. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/51307
-
- 11 Sep, 2018 1 commit
-
-
Yorick Peterse authored
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
-
- 07 Sep, 2018 1 commit
-
-
Jan Provaznik authored
-
- 02 Aug, 2018 1 commit
-
-
Jarka Kadlecová authored
This reverts commit 8717c7da.
-
- 30 Jul, 2018 1 commit
-
-
Bob Van Landuyt authored
The status is shown for - The author of a commit when viewing a commit - Notes on a commit (regular/diff) - The user that triggered a pipeline when viewing a pipeline - The author of a merge request when viewing a merge request - The author of notes on a merge request (regular/diff) - The author of an issue when viewing an issue - The author of notes on an issue - The author of a snippet when viewing a snippet - The author of notes on a snippet - A user's profile page - The list of members of a group/user
-
- 26 Jul, 2018 1 commit
-
-
gfyoung authored
Partially addresses #47424.
-
- 11 Jul, 2018 1 commit
-
-
Jarka Kadlecová authored
This reverts commit 4d9a3f42, reversing changes made to ecf9c145.
-
- 03 Jul, 2018 2 commits
-
-
Jarka Kadlecová authored
-
Jan Provaznik authored
* Group filtering now includes also issues/MRs from subgroups/subprojects * fixed due_date * Also DRYed todo controller specs
-
- 21 Jun, 2018 1 commit
-
-
Felipe Artur authored
-
- 20 Jun, 2018 2 commits
-
-
Sean McGivern authored
-
Satish Perala authored
-
- 05 Jun, 2018 1 commit
-
-
Sean McGivern authored
This is tricky: the query was being run in `ObjectStorage::Extension::RecordsUploads#retrieve_from_store!`, but we can't just add batch loading there, because the `#upload=` method there would use the result immediately, making the batch only have one item. Instead, we can pre-emptively add an item to the batch whenever an avatarable object is initialized, and then reuse that batch item in `#retrieve_from_store!`. However, this also has problems: 1. There is a lot of logic in `Avatarable#retrieve_upload_from_batch`. 2. Some of that logic constructs a 'fake' model for the batch key. This should be fine, because of ActiveRecord's override of `#==`, but it relies on that staying the same.
-
- 24 May, 2018 1 commit
-
-
Oswaldo Ferreira authored
We request Gitaly in a N+1 manner to build discussion diffs. Once the diffs are from different revisions, it's hard to make a single request to the service in order to build the whole response. With this change we solve this problem and simplify a lot fetching this piece of info.
-
- 07 May, 2018 1 commit
-
-
Mario de la Ossa authored
-
- 05 Apr, 2018 2 commits
-
-
Jan Provaznik authored
Updates notes-related services and rendering so this code can be easily used for group-scoped resources (specifically Epics). Related to gitlab-ee!5205
-
Douwe Maan authored
[10.6] Prevent notes on confidential issues from being sent to chat See merge request gitlab/gitlabhq!2366 # Conflicts: # app/helpers/services_helper.rb
-
- 03 Apr, 2018 1 commit
-
-
Jan Provaznik authored
-
- 07 Mar, 2018 1 commit
-
-
Jan Provaznik authored
* adds basic discussions API for issues and snippets * reorganizes notes specs (so same tests can be used for all noteable types - issues, MRs, snippets)
-
- 28 Feb, 2018 3 commits
-
-
Kamil Trzciński authored
This reverts commit 54a575f1, reversing changes made to c63af942.
-
Sean McGivern authored
Move uploads to object storage Closes #4163 See merge request gitlab-org/gitlab-ee!3867
-
Fatih Acet authored
-
- 05 Feb, 2018 1 commit
-
-
Andreas Brandl authored
Fixes #32282.
-
- 02 Feb, 2018 1 commit
-
-
Mario de la Ossa authored
-
- 01 Feb, 2018 1 commit
-
-
Micaël Bergeron authored
-
- 13 Dec, 2017 2 commits
-
-
Toon Claes authored
When a note is part of a discussion, the email sent out will be `In-Reply-To` the previous note in that discussion. It also `References` all the previous notes in that discussion, and the original issue. Closes gitlab-org/gitlab-ce#36054.
-
Toon Claes authored
When a note is part of a discussion, the email sent out should be `In-Reply-To` the previous note in that discussion. Closes gitlab-org/gitlab-ce#36054
-
- 12 Dec, 2017 1 commit
-
-
Yorick Peterse authored
This allows EE to re-use the object, making it easier to trigger indexing of the noteable.
-
- 07 Dec, 2017 3 commits
-
-
micael.bergeron authored
-
micael.bergeron authored
-
Douwe Maan authored
-
- 06 Dec, 2017 1 commit
-
-
Yorick Peterse authored
This throttles the number of UPDATE queries that can be triggered by calling "touch" on a Note, Issue, or MergeRequest. For Note objects we also take care of updating the associated "noteable" relation in a smarter way than Rails does by default.
-
- 27 Nov, 2017 1 commit
-
-
Douwe Maan authored
-
- 24 Nov, 2017 1 commit
-
-
Douwe Maan authored
-
- 21 Nov, 2017 1 commit
-
-
micael.bergeron authored
-