- 23 7月, 2019 1 次提交
-
-
由 Heinrich Lee Yu 提交于
When a user's notification email is set for a group, we should use that for pipeline emails
-
- 22 7月, 2019 3 次提交
-
-
由 Vladimir Shushlin 提交于
This validation prevents the domain from being saved from the UI e.g. when user tries to enable Let's Encrypt integration
-
由 Jan Provaznik 提交于
This pagination is not used anywhere so there is no reason to keep it. It seems the usage of offset_id was probably removed in 90c60138
-
由 Heinrich Lee Yu 提交于
Applies to issues_url and new_issue_url
-
- 20 7月, 2019 10 次提交
-
-
由 Nick Thomas 提交于
If `project_auto_devops.enabled` is nil for a project, when setting any auto devops values via the API, we try to create a new row in the DB, instead of re-using the existing one. This leads to the project_id being set to nil, and the database `NOT NULL` constraint leading to a 500 response. This commit resolves the issue by correctly detecting the presence of a ProjectAutoDevops row and re-using it. Persistence is also moved away from explicit `update!` calls and into relying on `autosave: true` on the model.
-
由 Fabio Papa 提交于
- Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
-
由 Fabio Papa 提交于
-
由 Fabio Papa 提交于
-
由 Fabio Papa 提交于
-
由 Fabio Papa 提交于
- Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
-
由 Fabio Papa 提交于
-
由 Fabio Papa 提交于
-
由 Fabio Papa 提交于
-
由 Fabio Papa 提交于
This setting is at the group level only. The default is specified to be maintainers and owners. **Specs only**, all failing.
-
- 19 7月, 2019 3 次提交
-
-
由 Tiger 提交于
If an environment slug is predictable given only the environment name, we can use the environment slug earlier in the CI variable evaluation process as we don't have to wait for the environment record itself to be persisted.
-
由 Thong Kuah 提交于
Also means we don't have to resort to an update statement to set parent for child groups who also have clusters. This is much shorter than ``` create(:cluster, :provided_by_gcp, :group, groups: [group]) ```
-
由 Eugenia Grieff 提交于
-
- 17 7月, 2019 6 次提交
-
-
由 Vladimir Shushlin 提交于
- Set access level in before_validation hook - Add post migration for updating existing project_features
-
由 Imre Farkas 提交于
By doing smaller mget calls to Redis, it can better schedule the workload. Currently a single mget with a lot of keys can keep Redis busy for long, while nothing in its queue gets processed.
-
由 Thong Kuah 提交于
This has been enabled on production without issue https://gitlab.com/gitlab-org/gitlab-ce/issues/64259
-
由 Reuben Pereira 提交于
Instead return error objects.
-
由 Małgorzata Ksionek 提交于
Change small things for better readability
-
由 João Cunha 提交于
- Set as uninstallable app - Update docs - Adjust specs
-
- 16 7月, 2019 1 次提交
-
-
由 Adam Hegyi 提交于
- Background migration for changing null values to false - Set false as default value for private_profile DB column
-
- 15 7月, 2019 3 次提交
-
-
由 Małgorzata Ksionek 提交于
Add specs for group level Update entities Update base classes Add groups-centric changes Update plan and review stage Add summary classes Add summary spec Update specs files Add to specs test cases for group Add changelog entry Add group serializer Fix typo Fix typo Add fetching namespace in sql query Update specs Add rubocop fix Add rubocop fix Modify method to be in sync with code review Add counting deploys from subgroup To group summary stage Add subgroups handling In group stage summary Add additional spec Add additional specs Add more precise inheritance Add attr reader to group level Fix rubocop offence Fix problems with specs Add cr remarks Renaming median method and a lot of calls in specs Move spec setup Rename method in specs Add code review remarks regarding module Add proper module name
-
由 Fabio Pitino 提交于
Keep feature flag disabled by default and turn off all functionality related to legacy triggers. * Block legacy triggers from creating pipeline * Highlight legacy triggers to be invalid via the UI * Make legacy triggers invalid in the model
-
由 George Koltsov 提交于
-
- 13 7月, 2019 1 次提交
-
-
由 Daniel Danner 提交于
-
- 12 7月, 2019 2 次提交
-
-
由 Vladimir Shushlin 提交于
-
由 Heinrich Lee Yu 提交于
Updates changed method names and fixes spec failures
-
- 11 7月, 2019 4 次提交
-
-
由 George Koltsov 提交于
-
由 Jarka Košanová 提交于
- handling properties needs to be skipped when creating test records in order to test the legacy data
-
由 Mario de la Ossa 提交于
When cache_collection_render runs we end up reading and writing things to redis even if we already have the rendered field cached in the DB. This commit avoids using redis at all whenever we have the field already rendered in the DB cache.
-
This brings the rspec-core version in line with the Gitaly changes and introduces Rails 5.1/5.2 improvements. Full CHANGELOG: https://github.com/rspec/rspec-rails/blob/master/Changelog.md
-
- 10 7月, 2019 4 次提交
-
-
由 Balasankar "Balu" C 提交于
Signed-off-by: NBalasankar "Balu" C <balasankar@gitlab.com>
-
由 Małgorzata Ksionek 提交于
Fix rubocop offences
-
由 Luke Duncalfe 提交于
A new `discussion_id` argument on the `createNote` mutation allows people to create a note within that discussion. The ability to lazy-load Discussions has been added, so GraphQL.object_from_id can treat Discussions the same as AR objects and batch load them. https://gitlab.com/gitlab-org/gitlab-ce/issues/62826 https://gitlab.com/gitlab-org/gitlab-ee/issues/9489
-
由 Bob Van Landuyt 提交于
Instead of setting the name of the namespace to the user's username, set it to the user's name. This is more consistent with how we name the routes: The route-name of a namespace is the human name of the routable. In the case of a user-namespace, this is the owner's name. When we change a user's name (both on create and update), we now also update the namespace-name to the user's name. This will make sure that if we also correctly update all the nested routes.
-
- 09 7月, 2019 2 次提交
-
-
由 Małgorzata Ksionek 提交于
-
由 Małgorzata Ksionek 提交于
-