#### Problem Project import/export currently uses the legacy `push_rules` table to export and import push rule records. A new `project_push_rules` table has been introduced (with a proper unique index on `project_id`) and the migration to this table is in progress (#499156). The project [import_export.yml](https://gitlab.com/gitlab-org/gitlab/-/blob/62844522861dc816c40958627a9cc8c0e61da34e/lib/gitlab/import_export/project/import_export.yml#L1299) still references the old `push_rules` relation. Once the `read_project_push_rules` and `write_project_push_rules` feature flags are enabled, import/export must use the new table to stay consistent. This was identified during investigation of #591680 and discussed in [this comment](https://gitlab.com/gitlab-org/gitlab/-/work_items/591680#note_3151341041). #### Proposal 1. Add the `project_push_rules` relation to the project `import_export.yml` file 2. Add corresponding tests for export and import of the new relation 3. Ensure uniqueness is enforced during import so duplicate project push rules are not created (the `project_push_rules` table already has a unique index on `project_id`) #### Related issues - #591680 - `ActiveRecord::RecordInvalid: Validation failed: Project has already been taken` - #499156 - Push rules table migration tracking - #593331 - Add group push rules to group import/export