Add MergeRequests::MergeData and create table
What does this MR do and why?
Add MergeRequests::MergeData and create table
This is the first step of merge related data extraction from merge_requests
table.
Here are a few things that are different from the original table
- Rename
merge_status
->mergeability_status
to make it clear what it is. Also, it is nowsmallint
instead ofVARCHAR
to make it more efficient at storing limited number of states. - Include
project_id
as a sharding key - Change type for
in_progress_merge_commit_sha
andmerge_commit_sha
fromVARCHAR
toBYTEA
to be consistent with other SHA columns and save storage - Rename
merge_when_pipeline_succeeds
->auto_merge_enabled
to reflect the current alias
References
#560932
Screenshots or screen recordings
Before | After |
---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #560932