Skip to content

Fix defaults for MR states and merge statuses

Yorick Peterse requested to merge default-values-for-mr-states into master

What does this MR do?

This ensures that merge_requests.state and merge_requests.merge_status both have a proper default value and NOT NULL constraint on database level. We also make sure to update any bogus rows first, without blowing up the database.

I'll apply these changes manually to so we don't need to wait for the next patch release.

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Merge request reports