mr-ks opened a new pull request, #7364:
URL: https://github.com/apache/incubator-devlake/pull/7364

   ### Summary
   It is now possible to choose remote repositories connected through 'service 
connections' as a data scope. Tasks in the `cicd` and `code` domains are 
performed based on the visibility of these repositories (public or private).
   
   ⚠️ This pull request includes a database migration. The 
`_tool_azuredevops_go_repos` is extended with the following columns.
   
   
   | name       | default value | reason                                        
                                                                    |
   
|------------|---------------|-------------------------------------------------------------------------------------------------------------------|
   | Type       | TfsGit        | Indicates the source provider (TfsGit, 
GitHub, ...), necessary to retrieve the `builds` from the Azure DevOps API |
   | IsPrivate  | false         | Required to build the blueprint, tasks from 
the domain `DOMAIN_TYPE_CODE` are excluded for private repositories   |
   | ExternalId | null          | Necessary to retrieve the `builds` from the 
Azure DevOps API                                                      |
   
   ### Does this close any open issues?
   Resolves #7307 
   
   ### Screenshots
   The Azure DevOps Go plugins now provide additional information about the 
current processed data scope.
   
   
![image](https://github.com/apache/incubator-devlake/assets/32308695/2b8295c5-303b-4112-81a9-95d5fd0785aa)
   
   ### Other Information
   `listAzuredevopsRemoteScopes` has been refactored to retrieve data scopes in 
parallel, reducing the user's waiting time. `Disabled` AzureDevOps repositories 
are not included in the list.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to