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 don't have time to read all issues, but I do care about things that could effect my work. In this case, I currently care about Redshift. So I didn't need to read [CT-3234] [Feature] Allow query-commenting for dbt test command #8870 which is about BigQuery. If this ticket had the label "adapter-bigquery" I could have easily skipped reading it.
Yes, I am already selective about the issues I read now, so this would be an additional level of filtering and add in the ability to expand to not miss something when the issue title isn't clear.
So why "adapter-multiple"? Because if you had to add each adapter label to each adapter issue that would add a lot of label noise. This label would be used if it affected more than one adapter. Also, if something effects multiple adapters it a) could need to be checked to see if it happens in an adapter that the issue filer doesn't have access to and/or b) could be a more foundational change to adapters worth knowing about or weighing in on.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Proposal
I'm proposing adding labels such as:
for use on issues in this repository.
Why?
Reference
Existing adapter labels
Beta Was this translation helpful? Give feedback.
All reactions