[JIRA] (JENKINS-45586) Recent Changes not updated when using GIT Shallow clone option

[thefriendlyco...@gmail.com (JIRA)]

Title: Message Title

Kevin Phillips commented on JENKINS-45586   Re: Recent Changes not updated when using GIT Shallow clone option Mark Waite haha - I'm guessing you are absolutely correct. However, if someone complains about a regression (aka: a change in previous behavior) when the previous behavior was incorrect is, well, questionable anyway. It's hard to maintain backwards compatibility AND fix incorrect behavior at the same time since the latter, by definition, changes the previous behavior. That being said, what if there were some way to control that at least... like maybe an option in the Git config that says "ignore modified files" or some-such? It could be disabled by default to maintain backwards compatibility and yet could be enabled for the rest of us who want to have accurate information on the Jenkins UI. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.