Is your feature request related to a problem? Please describe.
Links to existing GitHub repositories under the pretext that the repos will stay in GitHub is not supported as of today, even if we think that this is technically doable.
Describe the solution you'd like
When running the migration, we expect any links to GitHub commits/branches to be migrated to ADO development links. Both ADO and Jira would need to be integrated with the same GitHub organization at the time of migration. No repository mapping would be needed.
The behavior would be controlled by a boolean flag like --include-github-development-links in the configuration file.
Is your feature request related to a problem? Please describe.
Links to existing GitHub repositories under the pretext that the repos will stay in GitHub is not supported as of today, even if we think that this is technically doable.
Describe the solution you'd like
When running the migration, we expect any links to GitHub commits/branches to be migrated to ADO development links. Both ADO and Jira would need to be integrated with the same GitHub organization at the time of migration. No repository mapping would be needed.
The behavior would be controlled by a boolean flag like
--include-github-development-linksin the configuration file.Additional context
This feature request is a follow-up on https://github.com/solidify/jira-azuredevops-migrator/issues/1022