|
|
|
|
|
by mtmail
4177 days ago
|
|
You already split by programming language, that should be useful. I wonder if one could identify code vs configuration, maybe by pre-categorizing directory names. Plus 'secure' certain files. E.g. a positive list of developers that is allowed to touch conversion-rates.csv. A warning after edit is still better than nothing. |
|
We could definitely do the last one. How about sending an alert if someone who has hardly any experience in a particular language touches a file of that language. For example say I have little experience in js and I touched a js file, tenXer would send an alert saying that the lead or someone else on the team needs to review that commit more carefully? We could do the same with lines of code that are really old that have been changed or code that has been written by someone who is no longer at the company/ org.