Fine-grained control over repository selection

[hungrybluedev]

trafficstars

Describe the feature

1. The user might want to include only a certain number of repositories.
2. We may want to exclude certain repositories.
3. We may want to clone only private or only public repositories.

Use Case

1. At work, where users are only interested in synchronising a handful of repositories.
2. A private repo containing personal information that is not desirable in backups. Or something that contains a lot of data, with binary files, PDFs, etc that may already be backed up.
3. Users may want to store these repositories separately.

Proposed Solution

1. The listing mechanism should be able to filter based on user input.
2. Additional optional configuration information should be stored in the credential files.
3. We'd like to restrict the scope so that we have security by default: avoid cloning private repositories, focus on public ones only.
4. We'd like to support both exclude lists and include lists.
5. We'll probably not use regex - making the user explicitly spell out the repositories is important for acknowledgement, and informed consent.

Other Information

No response

Acknowledgements

• [X] I may be able to implement this feature request
• [ ] This feature might incur a breaking change

Version used

0.6.0

Environment details (OS name and version, etc.)

Irrelevant