Update GitHub Import to not use legacy_bulk_insert when creating issues
What does this MR do and why?
This update modifies GitHub Import to avoid using the legacy_bulk_insert
method while creating issues, similar to the approach used in the BitBucket importer.
legacy_bulk_insert
is unnecessary as callbacks can be skipped by providing the attribute importing
. Also, because legacy_bulk_insert
is no longer used, update_search_data
method does not need to be called as the Issue model includes PgFullTextSearchable which defines an after commit callback that updates the search data.
Related to: #439825 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
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
- Import a GitHub project that contains issues.
- Check if the issues where imported and that the full text search is working