If No, please run rush change before, this is necessary.
If adding a new feature, the PR's description includes:
[ ] Reason for adding this feature
[ ] How to use
[ ] A basic example
Does this PR introduce a breaking change? (check one)
[ ] Yes
[ ] No
If yes, please describe the impact and migration path for existing applications:
Summary
Improve the logic to check existence of a branch
Improve the logic to accurately report success data
Detail
git ls-remote --exist-code explicitly returns exit code 2 to indicate the branch is missing remotely. The new logic respects this logic, that says other exit code will be treated the branch exists remotely.
Previously, all data are sent via telemetry service. After this PR, data will be sent only for success commands.
Basic Checks
Have you run
rush changefor this change?If No, please run
rush changebefore, this is necessary.If adding a new feature, the PR's description includes:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
Summary
Detail
git ls-remote --exist-codeexplicitly returns exit code 2 to indicate the branch is missing remotely. The new logic respects this logic, that says other exit code will be treated the branch exists remotely.Previously, all data are sent via telemetry service. After this PR, data will be sent only for success commands.
How to test it
Local