No, not something automated like that. Though mention-bot seems to work decently well, it doesn't know for example that changes to all-packages.nix are much less useful than changes to a default.nix file in a package directory. A human can know that, and additionally look at the log messages to see the nature of the changes to see if they're likely to be relevant.
Bardur Arantsson <[email protected]> writes: > On 2016-09-02 23:16, Shea Levy wrote: >> Why can't people use the commit logs to see who is knowledgeable? > > Are you thinking of something like https://github.com/facebook/mention-bot ? > > This fails in the case where someone does a big cross-cutting (i.e. not > concerned with particular packages) refactor which happens to touch a > lot of code. Suddenly you'd get a huge number of notifications about > *every package under the sun*. > > (Why, yes, I *have* been the 'victim' of this type of thing in a GitHub > repo where the project uses mention-bot. Now, some of that may simply be > due to the algorithm that mention-bot uses, but it's pretty hard to > avoid unless you're *somehow* able to algorithmically distinguish > large-scale cross-cutting refactors from actual package maintenance > changes.) > > Regards, > > > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev
signature.asc
Description: PGP signature
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
