My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 3185: Overriding a label in a child project should not override all its properties and values
4 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by sschuberth, Feb 18, 2015
As documented at [1], the current behavior is that "Overriding a label in a child project overrides all its properties and values". This forces you to copy all properties that you do not want to override from the parent to the child project. This is error prone if you intention is to keep non-child-specific properties in sync with whatever the parent values are.

So how about overriding on a per-properties basis instead of a per-label basis? I.e., just introducing a label in a child that is already present in the parent should not override anything, but derive everything, unless you specifically re-define properties in the child.

[1] https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_custom
Sign in to add a comment

Powered by Google Project Hosting