Fix Git Version #5298
Open
Fix Git Version #5298
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @rajmishra1997, JFYI: we in Azure Repos team would also appreciate upgrading the version to the latest. There was a fix in 2.50 that is blocking compression of certain repos in ADO.
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tarunramsinghani
approved these changes
Sep 5, 2025
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
PR uses fork repository branch, which causes PR checks to fail (Token cannot be accessed by forked repository) hence closing this PR. Another PR: #5311 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Explain the context or motivation behind this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items
Upgrades Git for windows version, as version 2.49.0 contains a regression.
Fixes #5293
Git Issue: git-for-windows/git#5427
Description
Provide a concise summary of the changes introduced in this PR.
Git issue is fixed in Git version 2.50.0, hence upgraded version to latest version 2.51.0
Risk Assessment (Low / Medium / High)
Assess the risk level and justify your assessment. For example: code path sensitivity, usage scope, or backward compatibility concerns.
Medium
Unit Tests Added or Updated (Yes / No)
Indicate whether unit tests were added or modified to reflect the changes.
No
Additional Testing Performed
_List manual or automated tests performed beyond unit tests (e.g., integration, scenario, regression)._Tested locally by building locally, git 51.0 is fetched successfully
Change Behind Feature Flag (Yes / No)
Can this change be behind feature flag, if not why?
No, changes are limited to an .sh file
Tech Design / Approach
No, not required
Documentation Changes Required (Yes/No)
Indicate whether related documentation needs to be updated.
No
Logging Added/Updated (Yes/No)
No
Telemetry Added/Updated (Yes/No)
No
Rollback Scenario and Process (Yes/No)
No
Dependency Impact Assessed and Regression Tested (Yes/No)