Confirm Project forking behaviour via the API

* It's unclear that the forking operation can still be ongoing * `import_status` is available in Project Entity to determine status

Confirm Project forking behaviour via the API
cff037fd · Mark Fletcher · e34e5761 · cff037fd · cff037fd
Commit cff037fd authored Jun 06, 2017 by Mark Fletcher
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 0 deletions

28607-forking-and-configuring-project-via-api-works-very-unreliable.yml ...and-configuring-project-via-api-works-very-unreliable.yml +4 -0

projects.md doc/api/projects.md +2 -0

No files found.
--- a/changelogs/unreleased/28607-forking-and-configuring-project-via-api-works-very-unreliable.yml
+++ b/changelogs/unreleased/28607-forking-and-configuring-project-via-api-works-very-unreliable.yml
+---
+title: Confirm Project forking behaviour via the API
+merge_request:
+author:
--- a/doc/api/projects.md
+++ b/doc/api/projects.md
@@ -551,6 +551,8 @@ Parameters:

 Forks a project into the user namespace of the authenticated user or the one provided.

+The forking operation for a project is asynchronous and is completed in a background job. The request will return immediately. To determine whether the fork of the project has completed, query the `import_status` for the new project.
+
 ```
 POST /projects/:id/fork
 ```