delta/gitlab/gitlab-ce.git/db/post_migrate, branch winh-notes-service-toggleResolveNote gitlab.com: gitlab-org/gitlab-ce.git Remove old migrations and specs 2019-07-02T19:55:56+00:00 Heinrich Lee Yu heinrich@gitlab.com 2019-07-02T19:55:56+00:00 28ac2d304989164a1e9bf6d82fa8106a86a5f688 This removes old migrations that violate the FactoriesinMigrationSpecs cop 
This removes old migrations that violate the
FactoriesinMigrationSpecs cop
Squash old migrations 2019-07-02T08:35:03+00:00 Nick Thomas nick@gitlab.com 2019-07-01T11:23:25+00:00 cfe31f992a12c95570891b8cca8747589c6c6228 Use the `squasher` gem to squash migrations older than the start of 2018 
Use the `squasher` gem to squash migrations older than the start of 2018
refactor(db): remove Sentry from application settings, disable_ddl_transaction 2019-06-25T20:06:17+00:00 Roger Meier r.meier@siemens.com 2019-06-25T20:06:17+00:00 cd8aaea36f3c2b69c7c48c00ed56de14267969dd 






refactor(db): remove Sentry from application settings
2019-06-25T19:45:55+00:00

Roger Meier
r.meier@siemens.com

2019-06-25T19:15:26+00:00

f52101f20a2499c2c2e997e108482f63b1911ba2












refactor: remove Sentry from application settings
2019-06-25T19:17:19+00:00

Roger Meier
r.meier@siemens.com

2019-04-30T20:06:08+00:00

946ffc67b711b39512a789213779d2736fcc0049












Merge branch 'sync-merge-ref-upon-mergeability-check' into 'master'
2019-06-24T09:31:46+00:00

Douwe Maan
douwe@gitlab.com

2019-06-24T09:31:46+00:00

7821defab33f917b62d1132339a521d609f191d6

Automatically update MR merge-ref along merge status

See merge request gitlab-org/gitlab-ce!29569




Automatically update MR merge-ref along merge status

See merge request gitlab-org/gitlab-ce!29569






Merge branch 'db/update-geo-nodes-primary' into 'master'
2019-06-21T10:16:50+00:00

Andreas Brandl
abrandl@gitlab.com

2019-06-21T10:16:50+00:00

4dcbee4d26bc473f408384e61b4f412df6f574de

Disallow `NULL` values for `geo_nodes.primary` column

Closes gitlab-ee#12061

See merge request gitlab-org/gitlab-ce!29818




Disallow `NULL` values for `geo_nodes.primary` column

Closes gitlab-ee#12061

See merge request gitlab-org/gitlab-ce!29818






Merge branch '62772-migrate-managed-clusters-to-unmanaged' into 'master'
2019-06-21T01:26:19+00:00

Thong Kuah
tkuah@gitlab.com

2019-06-21T01:26:19+00:00

148516ba36855095fa995c2d4e8077919cdb6db6

Migrate managed clusters that aren't using managed features to unmanaged

Closes #62772

See merge request gitlab-org/gitlab-ce!29251




Migrate managed clusters that aren't using managed features to unmanaged

Closes #62772

See merge request gitlab-org/gitlab-ce!29251






Migrate clusters with no token to unmanaged
2019-06-20T22:30:26+00:00

Tiger
twatson@gitlab.com

2019-06-14T00:45:31+00:00

bae848418b1784be938bb670da4ffceed06f42dd

There are clusters that have Kubernetes namespaces
stored which are missing a service account token.
These namespaces are unable to be used for deployments,
so marking the clusters as unmanaged will allow the
platform credentials to be used instead.





There are clusters that have Kubernetes namespaces
stored which are missing a service account token.
These namespaces are unable to be used for deployments,
so marking the clusters as unmanaged will allow the
platform credentials to be used instead.







Automatically update MR merge-ref along merge status
2019-06-20T14:48:30+00:00

Oswaldo Ferreira
oswaldo@gitlab.com

2019-05-21T21:14:22+00:00

3af348b6cf28ef1d9d3025f7012049132b57798c

This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.

In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.

We've also updated the logic to be more systematic and less user-based.





This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.

In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.

We've also updated the logic to be more systematic and less user-based.