3 ms·
That's just going to cause annoying false positives, and it's not that difficult to get around such detection. I'll bet the only result would be confused devel
by ronsor 6y ago
That's just going to cause annoying false positives, and it's not that difficult to get around such detection.
I'll bet the only result would be confused developers.
- mehrdadn 6y agoI can imagine it failing or succeeding depending on how intrusive the UX is. It's worth trying out I think, especially in an opt-in fashion. They can improve it gradually and people can leave it disabled if they don't like it.
- katbyte 6y agoI presume it would be opt in, would make for a handy github action tbh
- mehrdadn 6y agoNote that it shouldn't be an "action" on GitHub Actions, since those are specified in the repo itself, and can hence be removed in the same commit. It needs to be an external thing.