[Bug] dbt enforced data_type checks doesn't check complex data types in Databricks #643
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# **what?** | |
# When the core team triages, we sometimes need more information from the issue creator. In | |
# those cases we remove the `triage` label and add the `awaiting_response` label. Once we | |
# recieve a response in the form of a comment, we want the `awaiting_response` label removed | |
# in favor of the `triage` label so we are aware that the issue needs action. | |
# **why?** | |
# To help with out team triage issue tracking | |
# **when?** | |
# This will run when a comment is added to an issue and that issue has to `awaiting_response` label. | |
name: Update Triage Label | |
on: issue_comment | |
defaults: | |
run: | |
shell: bash | |
permissions: | |
issues: write | |
jobs: | |
triage_label: | |
if: contains(github.event.issue.labels.*.name, 'awaiting_response') | |
uses: dbt-labs/actions/.github/workflows/swap-labels.yml@main | |
with: | |
add_label: "triage" | |
remove_label: "awaiting_response" | |
secrets: inherit # this is only acceptable because we own the action we're calling |