You can probably use something like
git clean -xdf
To get rid of all the artifacts not tracked by git, in this case it’s virtually the same as deleting the repo and re-cloning it.
NOTE: Make sure everyhing is staged, otherwise that data is gone
You can probably use something like
git clean -xdf
To get rid of all the artifacts not tracked by git, in this case it’s virtually the same as deleting the repo and re-cloning it.
NOTE: Make sure everyhing is staged, otherwise that data is gone
If they’re leaving them there, I’d be all for it
WTF is wrong with you people? All this effort just to be a dick.
The fine line between ssh and lsd
That’s passion my friend! Don’t underestimate it as just stubbornness
Some people simply ignore warnings, that’s the main issue. Trust me, I saw this way too often.
If you cannot compile it than you have to fix it, otherwise just mark unused variables as ‘not an error’ via _ = someunusedvar
.
It isn’t indeed, most people that are actually working in Italy don’t want it. It doesn’t help, it just gets people stuck not working indefinitely
Similarly, you can leverage this to wire traffic to DB replicas for instance. This if you need to handle traffic to DBs under specific scenarios (DB problems, burst of traffic, bugs, etc). So basically a purely technical feature flag (paying attention to authorization as always)
deleted by creator