Skip to content

Commit 6239ea6

Browse files
authored
Apply suggestions from code review
1 parent 3cf4d5f commit 6239ea6

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

modules/importing-repositories/procedure-managing-the-imported-repository-list.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ You can oversee and manage the repositories that are imported to the {product-sh
1010
. Click *Bulk Import* in the left sidebar to display all the current repositories that are being tracked as Import jobs, along with their status.
1111

1212
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.
1413
Note that it may take a few minutes for the entities to be available in the catalog.
1514

1615
Waiting for approval:: There is an open pull request adding a `catalog-info.yaml` file to the repository.
@@ -20,7 +19,6 @@ You can:
2019
* To transition the Import job to the _Added_ state, merge the import pull request from the Git repository.
2120

2221
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.
2422

2523
[NOTE]
2624
====

0 commit comments

Comments
 (0)