1kasa opened a new issue, #925: URL: https://github.com/apache/dubbo-go-samples/issues/925
description： In the dubbo-go-samples repository that the current integration test relies on, the main and develop branches differ significantly, resulting in inconsistent test sample environments used by CI in different branches, affecting the stability and comparability of test results. If you submit code to the dubbogo main branch, integration tests will pull down the dubbo-go-samples main branch for verification. If you submit code to the dubbogo develop branch, integration tests will pull down the dubbo-go-samples develop branch for verification. Here are two solutions I can think of: 1. Regularly synchronize the samples develop branch with the main code to ensure that the differences are not too large. 2. Modify the logic of the Dubbogo CI integration test to use a unified branch. 3. 3. To be determined (welcome to discuss) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
