It should be possible to define a condition and re-use it in several places. For instance, say you want to define a group of developers that may or may not do something (e.g. only certain people should be allowed to delete resource files). Then it would be nice to be able to define an "author condition" that checks whether the author (committer) is one of a specified set of authors and use this "author condition" in several compley conditions. So if the group changes you only have to change this one condition and not every compley condition that actually requires it.
Maybe this could be accomplished by giving conditions an optional name which that could then later be referred to in complex conditions.
BrightLight
commented
1 year ago
It should be possible to define a condition and re-use it in several places. For instance, say you want to define a group of developers that may or may not do something (e.g. only certain people should be allowed to delete resource files). Then it would be nice to be able to define an "author condition" that checks whether the author (committer) is one of a specified set of authors and use this "author condition" in several compley conditions. So if the group changes you only have to change this one condition and not every compley condition that actually requires it. Maybe this could be accomplished by giving conditions an optional name which that could then later be referred to in complex conditions.