Confirm Project forking behaviour via the API
requested to merge markglenfletcher1/gitlab-ce:28607-forking-and-configuring-project-via-api-works-very-unreliable into master
What does this MR do?
Docs only change
Confirms that the forking operation is an asynchronous one and the project's import status should be queried to determine whether the fork is complete
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Users forking projects using the API considered the forking operation complete once a response was received with the project data in the payload.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #28607 (closed)
Edited by username-removed-419655