fix: Re-enable creation of the new repositories

[strainovic]

Hi all,

This PR fixes issue safe-settings/issues/780.

The code that returns the list of all repositories does not include one that does not exist.

Cheers! 👋

[Copilot]

Pull Request Overview

This PR fixes the repository-fetch logic to include repos defined in the config but missing from the API response.

• Introduces tracking of processed repos to avoid duplicates
• Splits processing into existing and missing repos batches
• Concatenates and filters both result sets before returning

[klutchell]

This change still requires force_create: true, correct? Just making sure that repo creation is still opt-in and not the default behaviour.

[strainovic]

Hi @klutchell.

Yes, it requires force_create: true. It is here:

safe-settings/lib/plugins/repository.js

Line 121 in 3e5d4fe

if (this.force_create) {

Thanks

[Copilot]

Pull Request Overview

A fix to ensure newly configured repositories that aren’t returned by the installation API still get processed.

• Split repository handling into “existing” (via GitHub paginate) and “missing” (from configuration) batches
• Track which repos have been processed to avoid duplicates
• Concatenate results from both batches and filter out nulls

Comments suppressed due to low confidence (1)

lib/settings.js:508

• [nitpick] Rename repoInConfigs to something like configuredRepos or reposFromConfig to more clearly express its purpose.

const repoInConfigs = Object.values(this.repoConfigs)