[skip ci] Removing former Grunts #53
Conversation
| @@ -1 +1 @@ | |||
| * @brikis98 @pete0emerson | |||
There was a problem hiding this comment.
imho remove all, way to much formalism for such repo :)
There was a problem hiding this comment.
Um... this is such a critical repo for so many modules. Why do you think it needs LESS safeguards?
There was a problem hiding this comment.
this codeowners file is repo wide, not per folder.
any repowide codeowners can be done as gh repo config. right?
codeowners is useless here.
also codeowners does not state who allowed to modify code,
but gh tf config does.
more people can modify than listed in codeowners.
There was a problem hiding this comment.
see #64
in reality none codeowners looked or approved and yet merged.
so codeowners useless process here.
codeowners mostly for monorepos. this is not monorepo.
There was a problem hiding this comment.
not working sadeguard is LESS safeguards actually.
removing will add more by not obscuring reality.
so i suggest more security actually;) also gh tf.
[skip ci] Removing former Grunts