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
We often create a label in dbt-core and then want it to also appear in all other repos (dbt-snowflake, dbt-redshift, dbt-spark, dbt-bigquery, dbt-docs, and so on). Right now we manually create it everywhere.
It would be great to be able to run an action to copy a label from one repo to one-to-many others. The name, description and color should all match. If the label already exists in another repo, it would be ideal if we could overwrite it with the new color/description properties.
Solution:
A reusable workflow with a workflow_dispatch and workflow_call trigger. We could then have a workflow that copies from dbt-core to all repos listed under the Core GitHub team. Then the workflow could also be triggered manually to deliver to a subset of those repos.
The text was updated successfully, but these errors were encountered:
it reads all the colors from dbt-core and sets them as the same in a bunch of other repos. not sure how urgent this is, but I'd be interested to do this in Go after some recent learning in #51
--
actually I was going to do something like this for personal repos too -- it's annoying to manually setup labels + colors. so wouldn't take a dependency on me doing this if it has any urgency, but otherwise I'm interested!
Problem:
We often create a label in
dbt-core
and then want it to also appear in all other repos (dbt-snowflake
,dbt-redshift
,dbt-spark
,dbt-bigquery
,dbt-docs
, and so on). Right now we manually create it everywhere.It would be great to be able to run an action to copy a label from one repo to one-to-many others. The name, description and color should all match. If the label already exists in another repo, it would be ideal if we could overwrite it with the new color/description properties.
Solution:
A reusable workflow with a
workflow_dispatch
andworkflow_call
trigger. We could then have a workflow that copies fromdbt-core
to all repos listed under theCore
GitHub team. Then the workflow could also be triggered manually to deliver to a subset of those repos.The text was updated successfully, but these errors were encountered: