diff --git a/.github/workflows/docs-issues.yml b/.github/workflows/docs-issues.yml
deleted file mode 100644
index f49cf517c..000000000
--- a/.github/workflows/docs-issues.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-# **what?**
-# Open an issue in docs.getdbt.com when an issue is labeled `user docs` and closed as completed
-
-# **why?**
-# To reduce barriers for keeping docs up to date
-
-# **when?**
-# When an issue is labeled `user docs` and is closed as completed.  Can be labeled before or after the issue is closed.
-
-
-name: Open issues in docs.getdbt.com repo when an issue is labeled
-run-name: "Open an issue in docs.getdbt.com for issue #${{ github.event.issue.number }}"
-
-on:
-  issues:
-    types: [labeled, closed]
-
-defaults:
-  run:
-    shell: bash
-
-permissions:
-    issues: write # comments on issues
-
-jobs:
-  open_issues:
-    # we only want to run this when the issue is closed as completed and the label `user docs` has been assigned.
-    # If this logic does not exist in this workflow, it runs the
-    # risk of duplicaton of issues being created due to merge and label both triggering this workflow to run and neither having
-    # generating the comment before the other runs.  This lives here instead of the shared workflow because this is where we
-    # decide if it should run or not.
-    if: |
-      (github.event.issue.state == 'closed' && github.event.issue.state_reason == 'completed') && (
-      (github.event.action == 'closed' && contains(github.event.issue.labels.*.name, 'user docs')) ||
-      (github.event.action == 'labeled' && github.event.label.name == 'user docs'))
-    uses: dbt-labs/actions/.github/workflows/open-issue-in-repo.yml@main
-    with:
-        issue_repository: "dbt-labs/docs.getdbt.com"
-        issue_title: "Docs Changes Needed from ${{ github.event.repository.name }} Issue #${{ github.event.issue.number }}"
-        issue_body: "At a minimum, update body to include a link to the page on docs.getdbt.com requiring updates and what part(s) of the page you would like to see updated."
-    secrets: inherit
diff --git a/.github/workflows/release-branch-tests.yml b/.github/workflows/release-branch-tests.yml
index 2a84d1007..c4460975d 100644
--- a/.github/workflows/release-branch-tests.yml
+++ b/.github/workflows/release-branch-tests.yml
@@ -27,4 +27,5 @@ jobs:
     uses: dbt-labs/actions/.github/workflows/release-branch-tests.yml@main
     with:
       workflows_to_run: '["main.yml", "integration.yml"]'
+      include_main: false
     secrets: inherit
diff --git a/.github/workflows/triage-labels.yml b/.github/workflows/triage-labels.yml
deleted file mode 100644
index 91f529e3e..000000000
--- a/.github/workflows/triage-labels.yml
+++ /dev/null
@@ -1,31 +0,0 @@
-# **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