Issue with pipeline processor when pipelines depend in old repositories

[jtvcodes]

azure-devops-migration-tools/src/MigrationTools.Clients.AzureDevops.Rest/Processors/AzureDevOpsPipelineProcessor.cs

Line 365 in b8abcb2

string sourceRepositoryName = sourceRepositories.FirstOrDefault(s => s.Id == sourceRepoId)?.Name;

While executing a pipeline configuration on my ADO project, the application threw an error with the message System.ArgumentNullException: Value cannot be null. Parameter name: key . At first, I wasn't sure what was the problem, but I did some troubleshooting and found that two of my pipelines were referring to repositories that no longer existed. Then I checked the line of the code, and the source repository name is defaulting to null instead of a string. My proposed solution is to add a null coalesce to an empty string, I tested out and it ran showing me the two repositories that had the issue and could not be migrated.

string sourceRepositoryName = sourceRepositories.FirstOrDefault(s => s.Id == sourceRepoId)?.Name ?? string.Empty;

[MrHinsh]

Please submit a pull request for approval. We love it when folks get credit for their fixes.

1. Create a Fork of this repo
2. Creating a pull request from a fork

@tomfrenzel is generally responsible for AzureDevOpsPipelineProcessor.cs

[jtvcodes]

Done #1470