Clever Geek Handbook

Github Pull Requests: How can I prevent "unreasonable" tagging changes?

Our Github submit requests are complete "no change":

enter image description here

I usually understand that they are related to recent code changes that have been merged into this branch. But I thought one of the reasons for the merge was to absorb such changes and not have it in mind to consider them as differentiated code afterwards.

I have a vague feeling that this might be caused by inconsistent CR / LF settings ending with an end between the project team. but can't find any information that provides clarity on how to get to where I want: a github pull request should only show the true code differences between the two commits.

+3


source to share


1 answer


One way to deal with it is to add a ?w=1

diff to the end of the url so that it will only display lines that have no problem with spaces.



+4


source






More articles:


All Articles