Added database table for target branch rules
What does this MR do and why?
Added the DB table for the target branch rules feature
UP migration:
main: == [advisory_lock_connection] object_id: 223600, pg_backend_pid: 64565
main: == 20230718145747 CreateTargetBranchRules: migrating ==========================
main: -- create_table(:target_branch_rules)
main: -> 0.0100s
main: == 20230718145747 CreateTargetBranchRules: migrated (0.1313s) =================
main: == [advisory_lock_connection] object_id: 223600, pg_backend_pid: 64565
DOWN migration:
main: == [advisory_lock_connection] object_id: 223680, pg_backend_pid: 63237
main: == 20230718145747 CreateTargetBranchRules: reverting ==========================
main: -- drop_table(:target_branch_rules)
main: -> 0.0035s
main: == 20230718145747 CreateTargetBranchRules: reverted (0.0098s) =================
main: == [advisory_lock_connection] object_id: 223680, pg_backend_pid: 63237
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.