In addition to area pod project board tasks, we can now have issue label tasks. The task for applying the untriaged label is introduced with this, and the scripts apply that task to the machinelearning and fabricbot-config repositories.
Since the generated tasks now go beyond area pod tasks, a taskSource property is applied to generated tasks so that generated and non-generated tasks can be distinguished from one another. The area pod convention is left in place for that detection though so that the existing configs can be recognized; we will remove that compatibility once we apply the generated configs to each of the affected repos.
As part of the factoring for this, the rules for isTriaged and isNotTriaged are extracted and parameterized based on which labels indicate an issue is triaged in each repository.
Contributes to #10
In addition to area pod project board tasks, we can now have issue label tasks. The task for applying the untriaged label is introduced with this, and the scripts apply that task to the machinelearning and fabricbot-config repositories.
Since the generated tasks now go beyond area pod tasks, a
taskSourceproperty is applied to generated tasks so that generated and non-generated tasks can be distinguished from one another. The area pod convention is left in place for that detection though so that the existing configs can be recognized; we will remove that compatibility once we apply the generated configs to each of the affected repos.As part of the factoring for this, the rules for
isTriagedandisNotTriagedare extracted and parameterized based on which labels indicate an issue is triaged in each repository.