From ddab48a3b4e3994f51ea11baeca24d9eed6cca5b Mon Sep 17 00:00:00 2001
From: Martin Atkins <mart@degeneration.co.uk>
Date: Tue, 22 Sep 2020 14:41:18 -0700
Subject: [PATCH] hashibot: Temporarily disable issue migration

The bot seems to currently be running into some operational problems that are
creating noise for provider development teams by potentially migrating issues
multiple times.

This is just a tactical change to stop the annoying symptoms right now, to
give some time to figure out what's actually going on here.
---
 .hashibot.hcl | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.hashibot.hcl b/.hashibot.hcl
index a71a88c91..f1a89efea 100644
--- a/.hashibot.hcl
+++ b/.hashibot.hcl
@@ -3,6 +3,7 @@ behavior "remove_labels_on_reply" "remove_stale" {
   only_non_maintainers = true
 }
 
+/*
 poll "label_issue_migrater" "provider_migrater" {
   schedule                = "0 20 * * * *"
   new_owner               = env.PROVIDERS_OWNER
@@ -23,6 +24,7 @@ poll "label_issue_migrater" "provider_migrater" {
     EOF
   migrated_comment = "This issue has been automatically migrated to ${var.repository}#${var.issue_number} because it looks like an issue with that provider. If you believe this is _not_ an issue with the provider, please reply to ${var.repository}#${var.issue_number}."
 }
+*/
 
 poll "closed_issue_locker" "locker" {
   schedule                      = "0 50 1 * * *"