chore: remove repos from integrations.settings column for github and github-nango integrations (CM-1005)

[themarolt]

Note

High Risk
Includes a data-migrating SQL script and broad changes to GitHub/GitHub-Nango mapping and worker execution paths; mistakes could drop repo visibility or break onboarding/sync runs.

Overview
GitHub repo metadata is no longer stored in integrations.settings. A new migration backs up existing settings, removes orgs[].repos plus legacy top-level repos/unavailableRepos for non-mapping GitHub integrations, and the backend now rehydrates settings.orgs[].repos from public.repositories when returning integrations.

GitHub/GitHub-Nango flows were updated to write repos only to public.repositories: mapping now preserves forkedFrom via an explicit map, strips repo fields from settings after unified repo sync, and triggers integration runs after transaction commit so workers can see the new rows. Worker/cron/nango code paths that previously iterated settings.orgs[].repos now call getReposForGithubIntegration or populateGithubSettingsWithRepos, and the legacy GitHub stream processor stops writing repos back into settings (keeps only unavailableRepos).

^{Written by Cursor Bugbot for commit d3f6b90. This will update automatically on new commits. Configure here.}

[cursor]

Duplicated repo-population logic across two layers

Low Severity

_populateRelations in integrationRepository.ts and populateGithubSettingsWithRepos in repositories/index.ts contain nearly identical logic: query repos from public.repositories, group by owner, and merge into settings.orgs[].repos. They differ only in ORM (Sequelize vs pg-promise) and in whether legacy keys are stripped. This duplication risks future divergence — a bug fix or schema change applied to one but not the other.

Additional Locations (1)

• services/libs/data-access-layer/src/repositories/index.ts#L605-L636

 

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}