Imports / Exports in Rails Cheatsheet is outdated per updates made in 12.1
<!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve <!-- Include the following detail as necessary: * What product or feature(s) affected? * What docs or doc section affected? Include links or paths. * Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs? * Any other ideas or requests? --> ### Further details <!-- * Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A --> ### Proposal Currently, our cheatsheet reflects this code snippet to check for Import/Export errors: ``` # Find the project and get the error p = Project.find_by_full_path('<username-or-group>/<project-name>') p.import_error # To finish the import on GitLab running version before 11.6 p.import_finish # To finish the import on GitLab running version 11.6 or after p.import_state.mark_as_failed("Failed manually through console.") ``` As of 12.1, the column that allowed us to call the attribute `:import_error` was removed per [this Merge Request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/14288). We should remove this section and replace with a redirect to the Project import status API. ### Who can address the issue <!-- What if any special expertise is required to resolve this issue? --> ### Other links/references Discovered when working on [this ticket](https://gitlab.zendesk.com/agent/tickets/173892) (ZD Internal)
issue