Mark Waite

> I need clarity. Should i stop working on it? Yes, I think you should stop working on it unless you can show that it is an issue with the...

> @mawinter69 @MarkEWaite Any objections to reopening and re-evaluating this? No objections from me.

> [@oleg-nenashev](https://github.com/oleg-nenashev) please assign me this. We don't assign issues to new contributors. Your comment is enough to allow you to start work on the issue. Your pull request is...

I would like more time to review the impact of the changes. If the changes are large enough that they require users to modify their Pipeline definitions, there will be...

+1 That is the plan that was discussed in the Platform SIG as well. No further updates to the Almalinux container image

Removed by: * #1937

I've included the issue description in the pull request description because it helps reviewers to have the issue described clearly in the pull request, without requiring that they open the...

> I was not able to fix the test case for `jgit` and `jgitapache`. I know the test executes this part of the code. At the location where you're looking,...

Interactive testing of the pull request shows that a leading space in the refspec from the UI still fails to clone. The job definition is: ```xml false 2 origin +refs/heads/3.11.x:refs/remotes/origin/3.11.x...

> @MarkEWaite @gounthar, Can you please review & tell the changes that needs to be done further, I am ready to update & implement them. I won't be able to...