Reports with connection to published dataset gets confused when saved in PBIP in same folder

[FireFighter1017]

When a report that uses a live connection to a published dataset is saved in PBIP format in the same folder as the dataset (github repo for example), it sometimes gets connected using a "byPath" connection which then makes Power BI Desktop that it has its own dataset (which is not true) and will apply changes to the dataset's ".SemanticModel" folder even though we haven't made any changes to the dataset.

Here you can see that a report named "EAM-Backlog-Report" have only a ".Report" folder and no ".SemanticModel" folder and that's because it was designed to be connected live to a dataset named "EAM-Backlog Dataset".

But in the "definition.pbir" file, the connection points to a relative path and if I try to open the report, it will not show this message in the status bar: 

And you will be able to modify power query scripts, relationships and columns, just as if you openned the actual dataset object instead of the report.

I understand that's how deployment pipelines are able to connect to report to the dataset that is in the same workspace.

But that causes some headaches when using Git repos and the reports are making unwanted changes to dataset.

My request is for reports that have a live connection could use a byPath connection but do not allow modification of the dataset.