Hi Matt, There is currently no way to exclude certain directories from requiring a bug id and commit message. Such a feature would be beneficial though, and it should be implemented in the access-control policy.
http://bugzilla.mkgnu.net/show_bug.cgi?id=859 A workaround at the moment is to create a bug id for documentation and always commit against that bug such documentation artifacts. Arguably, this may not be just a workaround: you should be tracking such documentation :) On Fri, 2010-10-15 at 19:38 -0500, Matt Woelfel wrote: > I have a repository with scmbug configured to require a bug id and a > minimum message length. In this repository there is a folder for > internal documentation, weekly meeting notes, etc, which I'm told did > not require a bug id or commit message before the upgrade, which makes > sense since we don't create new bugzilla entries for documentation > updates. > > Is there a way to exclude certain directories from requiring a bug id > and commit message? > > Thanks, > > Matt > _______________________________________________ > scmbug-users mailing list > [email protected] > http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
