| Age | Commit message (Collapse) | Author |
|---|
|
Adds event enum column to DesignsVersions join table
See merge request gitlab-org/gitlab-ce!30745
|
|
It needs to default to an empty array logically.
|
|
`Array.reverse_each` is faster than `Array.reverse.each` because:
* reverse.each creates a new array then loops each element
* reverse_each loops in reverse order (no intermediate array created)
|
|
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14597
See merge request gitlab-org/gitlab-ce!30520
|
|
Also adds index to support scopes and queries
This supports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14656
|
|
* Limits raw requests to 300 per minute and per raw path.
* Add a new attribute to ApplicationSettings so user can change this
value on their instance.
* Uses Gitlab::ActionRateLimiter to limit the raw requests.
* Add a new method into ActionRateLimiter to log the event into auth.log
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/48717
|
|
Signed-off-by: Istvan szalai <istvan.szalai@savoirfairelinux.com>
|
|
This is the first part of Docker Registry replication
for secondary Geo node.
|
|
Remove dead mysql code
Closes #63191
See merge request gitlab-org/gitlab-ce!29608
|
|
None of this code can be reached any more, so it can all be removed
|
|
This is no longer needed with Rails 5.2. opclass is the attribute used
per https://github.com/rails/rails/pull/19090/files.
Now that we've removed the monkey patch and restored the Rails schema
dumper, it appears Rails has dropped the inclusion of `using: :btree` as
well (https://github.com/rails/rails/pull/27981).
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64529
|
|
Add index for issues on relative position, project, and state for manual sorting
See merge request gitlab-org/gitlab-ce!30542
|
|
We also scope the `rescue`s to only those raised by ActiveRecord, which
would have allowed us to spot this logic error sooner.
|
|
|
|
and state
|
|
|
|
|
|
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
|
|
|
|
|
|
|
Adds migration to introduce non-regular rule_types to
approval_project_rules
|
|
- Set access level in before_validation hook
- Add post migration for updating existing project_features
|
|
- Background migration for changing null values to false
- Set false as default value for private_profile DB column
|
|
This eliminates conflicts between CE and EE db/schema.rb files.
|
|
This makes the CE and EE tables consistent and ensures changes in the
schema for the CE version don't cause conflicts with EE.
|
|
Add cleanup migration for MR's multiple assignees
See merge request gitlab-org/gitlab-ce!30269
|
|
Set the name of a user-namespace to the user name
See merge request gitlab-org/gitlab-ce!23272
|
|
Updates changed method names and fixes spec failures
|
|
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
|
In order to avoid confusion between Gitlab::Importers module and other
like named modules, this renamed it to Gitlab::DatabaseImporters.
|
|
Remove CommonMetricsImporter patch and change all references to
CommonMetrics::Importer. Move specs into their appropriate folders. Also
cleans up some common_metric importer namespacing.
|
|
This moves our metric importers into the lib folder. This will allow
them to be autoloaded instead of having to explicitly require them.
|
|
This refactors common metrics importer for two reasons. 1. To create a
new pattern that can be followed by future importers that will minimize
dependency collision and 2. To allow EE to more easily extend
dependencies.
|
|
This fixes the `Namespace#name` and `Route#name` for all user
namespaces and their personal projects in case they don't match the
user name anymore.
More info info in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23272
|
|
The migration steals the remaining background jobs
of populating MRs with assignees, executes them
synchronously and then makes sure that all the
assignees are migrated
|
|
into 'master'
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14328
See merge request gitlab-org/gitlab-ce!30003
|
|
Remove unused Gitaly feature flags
See merge request gitlab-org/gitlab-ce!30302
|
|
|
|
|
|
When GitLab was migrating to Gitaly, feature flags were used. These are
now out of use, and essentially a no-op. But they do make the output of
chatops ugly and the feature table is selected in full by the
application.
|
|
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
|
|
|
Remove old migration specs that violate FactoriesInMigrationSpecs
See merge request gitlab-org/gitlab-ce!30280
|
|
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
|
This removes old migrations that violate the
FactoriesinMigrationSpecs cop
|
|
This new attribute is optional and used when set instead of the default
format `gitlab+deploy-token-#{id}`.
Empty usernames will be saved as null in the database.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.
|
|
Use title and description fields for issue trackers
Closes #63690
See merge request gitlab-org/gitlab-ce!30096
|
|
- instead of using properties
- backward compatibility has to be kept for now
|
|
|
