- May 07, 2019
-
-
Removed the conditions added to Project.with_feature_available_for_user, and moved to the IssuableFinder. Now, we ensure that, in the projects retrieved in the Finder, the user has enough access for the feature.
-
- Apr 23, 2019
-
-
Model.new.attributes now also returns encrypted attributes.
-
- Apr 12, 2019
-
-
Martin Wortschack authored
- Update PO file
-
It's not needed anymore as we've replaced boolean `support_bot` with enum `bot_type`.
-
- Apr 05, 2019
-
-
Add columns to store project creation settings Add project creation level column in groups and default project creation column in application settings Remove obsolete line from schema Update migration with project_creation_level column existence check Rename migrations to avoid conflicts Update migration methods Update migration method
-
Brandon Labuschagne authored
Truncate existing users names which exceed 128 characters Include test for truncating users names
-
- Mar 28, 2019
-
-
Nick Thomas authored
-
- Mar 22, 2019
-
-
Logan King authored
-
-
- Mar 06, 2019
-
-
Andrew Newdigate authored
This style change enforces `return if ...` instead of `return nil if ...` to save maintainers a few minor review points
-
- Mar 05, 2019
-
-
Horatiu Eugen Vlad authored
Renamed EmailValidator to DeviseEmailValidator to avoid 'email:' naming collision with ActiveModel::Validations::EmailValidator in 'validates' statement. Make use of the options attribute of the parent class ActiveModel::EachValidator. Add more options: regex.
-
- Feb 19, 2019
-
-
Stan Hu authored
Ruby 2.6 introduced `Enumerable#filter`, which takes no arguments. Attempting to call `filter` on an `ActiveRecord::Relation` with a scope will fail with a `wrong number of arguments (given 1, expected 0)` message because the `Enumerable#filter` implementation overrides the delegated `ActiveRecord::Relation#filter` method. To make Admin::UsersController compatible with Ruby 2.6, rename `User.filter` to `User.filter_items`.
-
- Feb 13, 2019
-
-
Luke Bennett authored
These are backend changes. Use Vue for the import feature UI for "githubish" providers (GitHub and Gitea). Add "Go to project" button after a successful import. Use CI-style status icons and improve spacing of the table and its component. Adds ETag polling to the github and gitea import jobs endpoint.
-
- Feb 08, 2019
-
-
Bob Van Landuyt authored
-
- Feb 06, 2019
-
-
Fabian Schneider authored
-
- Feb 05, 2019
-
-
Brandon Labuschagne authored
The columns 'Created on' and 'Last activity' have been added to the admin -> users view. Sorting options have also been added for last activity and the search bar has been moved to match the issues page.
-
- Jan 31, 2019
-
-
Group guests will only be displayed merge requests to projects they have a access level to, higher than Reporter. Visible projects will still display the merge requests to Guests
-
- Jan 24, 2019
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Jan 21, 2019
-
-
Group guests will only be displayed merge requests to projects they have a access level to, higher than Reporter. Visible projects will still display the merge requests to Guests
-
- Jan 15, 2019
-
-
Mark Chao authored
-
- Dec 19, 2018
-
-
Jarka Košanová authored
- we now use the hierarchy class also for epics - also rename supports_nested_groups? into supports_nested_objects? - move it to a concern
-
-
- Dec 13, 2018
-
-
Alessio Caiazza authored
This commit adds a name to each release, defaulting it to tag name, keeps track of the SHA when a new release is created and tracks the current user as release author.
-
- Nov 26, 2018
-
-
Imre Farkas authored
-
- Nov 19, 2018
-
-
Nick Thomas authored
Private commit emails were introduced in !22560, but some parts of GitLab were not updated to take account of them. This commit adds support in places that were missed.
-
- Nov 07, 2018
-
-
Tiago Botelho authored
The private commit email is automatically generated in the format: id-username@noreply.HOSTNAME GitLab instance admins are able to change the HOSTNAME portion, that defaults to Gitlab's hostname, to whatever they prefer.
-
- Nov 05, 2018
-
-
Imre Farkas authored
find_by_token is overriden by TokenAuthenticatable which can be easily missed or confused with #find_by(:token) defined by ActiveRecord. First step for safer usage is to remove #find_by.
-
- Nov 01, 2018
-
-
Yorick Peterse authored
This moves the `where` in the `has_many :keys` association in Project to the Key model. This allows EE to override this method, instead of modifying the source code directly.
-
Yorick Peterse authored
This moves the `1.hour` constant used as the LDAP sync time to a separate method. This allows EE to override this method using a module, instead of directly modifying the source code.
-
- Oct 29, 2018
-
-
[11.4] Fix Token lookup for Git over HTTP and registry authentication See merge request gitlab/gitlabhq!2577
-
-
- Oct 26, 2018
-
-
Jasper Maes authored
-
- Oct 23, 2018
-
-
- Oct 18, 2018
-
-
- Oct 12, 2018
-
-
- Oct 08, 2018
-
-
Yorick Peterse authored
This refactors the TodoService class according to our code reuse guidelines. The resulting code is a wee bit more verbose, but it allows us to decouple the column names from the input, resulting in fewer changes being necessary when we change the schema. One particular noteworthy line in TodoService is the following: todos_ids = todos.update_state(state) Technically this is a violation of the guidelines, because `update_state` is a class method, which services are not supposed to use (safe for a few allowed ones). I decided to keep this, since there is no alternative. `update_state` doesn't produce a relation so it doesn't belong in a Finder, and we can't move it to another Service either. As such I opted to just use the method directly. Cases like this may happen more frequently, at which point we should update our documentation with some sort of recommendation. For now, I want to refrain from doing so until we have a few more examples.
-
- Sep 24, 2018
-
-
Tiago Botelho authored
-
- Sep 17, 2018
-
-
Brett Walker authored
Pass the 'non_archived' flag to finder methods
-
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
-
- Sep 16, 2018
-
-
Stan Hu authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/51530
-