Skip to content

Commit 1e41dfd

Browse files
committed
update FAQ
1 parent 4baab55 commit 1e41dfd

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

about/faq.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,9 @@ If you've set up your repository within the **LLNL organization**, you don't nee
164164
* See also [GitHub's instructions](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) for transferring a repo.
165165
* Sometimes the transferring organization wants to retain a copy (mirror or fork) of the repo, or a project lead "takes" the repo with them to another organization.
166166

167-
* **Standalone organization.** Alternatively, if you do not wish to transfer your repo, you can instead submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) with your organization and/or repository names. List your organization under the `"orgs"` line *only if you intend for all of its repositories to be included in the catalog* (e.g., `glvis`); otherwise, list only the repository under the `"repos"` line within the context of your organization (e.g., `hpc/spindle`).
167+
* **Standalone organization.** Alternatively, if you do not wish to transfer your repo, you can instead submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) with your organization and/or repository names. List your organization under the `"orgs"` line *only if you intend for all of its repositories to be included in the catalog* (e.g., `glvis`); otherwise, list only the repository under the `"repos"` line within the context of your organization (e.g., `ceed/laghos`).
168+
169+
* If you transfer your repo *from* a standalone organization into the LLNL org, please remove it from `"orgs"` in the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json). You don't need to explicitly add it to the LLNL org in the JSON file; all public repos under the LLNL org are automatically pulled into the catalog.
168170

169171
If you have a **project logo**, please follow the [Contributing Guidelines](/about/contribute) (see the question [How do I change how a specific repo appears in the catalog?](https://software.llnl.gov/about/contribute/#catalog)) for naming and uploading the file. If your repo is part of a non-LLNL organization that has its own avatar, that image will automatically display next to the repo name in the catalog, unless superseded by a repo-specific logo.
170172

0 commit comments

Comments
 (0)