Mark Waite

Closing because tests have not been added to confirm the new behavior works as expected.

> Any chances this will get re-opened and re-evaluated? It seems it would fix a problem that has been plaguing us for years now (https://issues.jenkins.io/browse/JENKINS-23606) With my current workload, there...

> in case of switch to JGit implementation the git command is not available to the workspace to the shell bat step That's correct. Command line git is the canonical...

Let's use a separate chapter. The "Installing" chapters are already long enough.

Thanks @Vandit1604 and @tanujdevops

I've added it to the [plugins.txt file](https://github.com/MarkEWaite/docker-lfs/blob/e0adf13aeca33f2d0809ad0f22e32eba357c4e0a/plugins.txt#L153) that I'm using for my [testing of git plugin 5.0.0 and git client plugin 4.0.0](https://community.jenkins.io/t/testing-git-plugin-5-0-0-and-git-client-plugin-4-0-0/5014/5). I'll include the details of [JENKINS-42971](https://issues.jenkins.io/browse/JENKINS-42971) in my...

I've confirmed that the incremental release of this pull request resolves [JENKINS-42971](https://issues.jenkins.io/browse/JENKINS-42971). I tested with the git plugin 5.0.0 pre-release and the git client plugin 4.0.0 pre-release.

> > Thanks! Approved > > Thank you :). Hmm just a quick question, how does the merging process work here? Who will merge this or we need more approvals?...

I found no issues related to this change in my [testing](https://community.jenkins.io/t/testing-git-plugin-5-0-0-and-git-client-plugin-4-0-0/5014/6) of git plugin 5.0.0 and git client plugin 4.0.0. I would like to see it merged and released. Thanks...

@Moofasax and @idrislaw the comment from the earlier message applies to you as well. You could adopt the plugin, merge the pull request, and release it. It would help you...