After a quick analysis of the problem, I found that this asterisk in the LabVIEW Project Explorer appears after I add an FPGA target to the project. This gives me a clue that the problem can be because of a difference with the NI CompactRIO Drivers version installed on my Windows machine and Te-Wei's Windows machine. After I checked the results from the git diff command in Te-Wei's laptop, I noted a text added to almost the end of the result: [rSeriesConfig.Begin][rSeriesConfig.End]. This is shown in the attached image gitDiff1a. NI-MAX shows which software and version are installed on a computer, so if we compare Te-Wei's computer and Patricio's computer, we can see in niMaxCompare.png attached image that there is the NI R Series Multifunction RIO 18.0 driver installed in Te-Wei's laptop and not installed in Patricio's laptop, which can generate this inconsistency in drivers detection by the LabVIEW Project Explorer, showing the asterisk on it. I will reinstall the NI Device Drivers on my laptop with the same drivers and version as Te-Wei's computer, and let's see if this solves the problem.

After I reinstalled the LabVIEW 2018 SP1, LabVIEW Real-Time Module 2018, LabVIEW FPGA Module 2018, and NI Device Drivers May, 2018 on my laptop (Windows 10), opened the LabVIEW project ts_m2fpga, pushed this project to the repo, I asked Te-Wei pull the project again in his Windows machine. Fortunately, he realized the asterisk disappeared on the LabVIEW Project Explorer in resultsFromTeWei.png.

It looks like the dependency is key and we may need to document it.