You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking about my label use cases, and I find that on most of my repositories, I've gotten into the habit of a label schema if you will. Things like type/xxxx or area/yyyy, status/zzz, and so on.
I'm trying to think of a forwards compatible mode where you could adorn a label with a property, and if that property matches an optional input file schema, would get color and prefix from the input schema.
I've been thinking about my label use cases, and I find that on most of my repositories, I've gotten into the habit of a label schema if you will. Things like
type/xxxx
orarea/yyyy
,status/zzz
, and so on.I'm trying to think of a forwards compatible mode where you could adorn a label with a property, and if that property matches an optional input file schema, would get color and prefix from the input schema.
Here's an off-the-cuff example:
Then, in my label file, we'd have a new optional property called category:
The merged labels would look like this:
I would perhaps call this like so:
Thoughts?
The text was updated successfully, but these errors were encountered: