Likewise, what happens if someone does a npm install or slap a venv or some other thing like that, before adding the equivalent of a gitignore for these things? Did you then just flood two times 200 MB worth of changes into the tracker? What if I just simply build in golang to a subfolder early on, is that v0.0.1 stuck there until someone decides to do the second layer of githistory inspection?
Perhaps not. But I'm not going to be the guy training the Team on how not to do it. They have shaky grasp of the full set of standards for PR's as is.
Likewise, what happens if someone does a npm install or slap a venv or some other thing like that, before adding the equivalent of a gitignore for these things? Did you then just flood two times 200 MB worth of changes into the tracker? What if I just simply build in golang to a subfolder early on, is that v0.0.1 stuck there until someone decides to do the second layer of githistory inspection?
Perhaps not. But I'm not going to be the guy training the Team on how not to do it. They have shaky grasp of the full set of standards for PR's as is.