Failed repositories on the source page
Overview
After a migration, one Git source can hold hundreds of repositories. A single webhook failure marked the whole source Disconnected, so the operator could not see which repositories to remove.
How it works
The init report is read per repository. The source stays connected while at least one repository succeeded. Failed repositories are shown on the source page and in edit, where each one can be removed.
Key files
src/core/data/data.service.ts- disconnect rule is per init unitsrc/protocol/source/ftp/ftp.service.ts- skip failed pathssrc/protocol/source/email/email.service.ts- skip a failed mailboxui/src/pages/workflows/- source page, edit table, connection badgeui/src/protocol/tower.mock.ts- demo GitLab repositories in failureui/src/shared/theme/joyTheme.ts- orange and neutral shades used by chips and filtersdocs/user/configuration/sources.md- failed repositories (EN and FR)docs/user/operations/troubleshooting.md- how to remove them (EN and FR)package.json-follow-redirects1.16.1 andpicomatch4.0.7.snykandui/.snyk- ignore the picomatch advisory that has no patched release, until 2027-01-20
Known issues
- None recorded in the 3.2.0 fragment.
Next steps
- None from this release.