You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/importing-repositories/procedure-managing-the-imported-repository-list.adoc
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,6 @@ You can oversee and manage the repositories that are imported to the {product-sh
10
10
. Click *Bulk Import* in the left sidebar to display all the current repositories that are being tracked as Import jobs, along with their status.
11
11
12
12
Added:: The repository is added to the {product-short} catalog after the import pull request is merged or if the repository already contained a `catalog-info.yaml` file during the bulk import.
13
-
This can be the case after the import PR has been merged, or if the repository already had a `catalog-info.yaml` when it was bulk-imported.
14
13
Note that it may take a few minutes for the entities to be available in the catalog.
15
14
16
15
Waiting for approval:: There is an open pull request adding a `catalog-info.yaml` file to the repository.
@@ -20,7 +19,6 @@ You can:
20
19
* To transition the Import job to the _Added_ state, merge the import pull request from the Git repository.
21
20
22
21
Empty:: {product-short} is unable to determine the import job status because the repository is imported from other sources but does not have a `catalog-info.yaml` file and lacks any import pull request adding it.
23
-
This can be the case if the repository was imported from other sources but does not have any `catalog-info.yaml` file and does not have any import PR adding it.
0 commit comments