From 2488d17d0c68f68aa518ee209ec4072ff1e9b7a5 Mon Sep 17 00:00:00 2001
From: "d.kaneshiro" <d.kaneshiro@churadata.okinawa>
Date: Thu, 18 May 2023 11:31:51 +0900
Subject: [PATCH 1/3] Added note before running integration tests

---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 893979fd9ac..11568f6833f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -113,7 +113,7 @@ When installed in this way, any changes you make to your local copy of the sourc
 
 With your virtualenv activated, the `dbt` script should point back to the source code you've cloned on your machine. You can verify this by running `which dbt`. This command should show you a path to an executable in your virtualenv.
 
-Configure your [profile](https://docs.getdbt.com/docs/configure-your-profile) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate.
+Configure your [profile](https://docs.getdbt.com/docs/configure-your-profile) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate.Make sure to create a profile before running integration tests.
 
 ## Testing
 

From e6111104012cb9c46b3af0ad2dad2f7fbe3398f3 Mon Sep 17 00:00:00 2001
From: "d.kaneshiro" <d.kaneshiro@churadata.okinawa>
Date: Thu, 25 May 2023 10:40:30 +0900
Subject: [PATCH 2/3] add CHANGELOG entries

---
 .changes/unreleased/Docs-20230525-103918.yaml | 6 ++++++
 1 file changed, 6 insertions(+)
 create mode 100644 .changes/unreleased/Docs-20230525-103918.yaml

diff --git a/.changes/unreleased/Docs-20230525-103918.yaml b/.changes/unreleased/Docs-20230525-103918.yaml
new file mode 100644
index 00000000000..bc2e2765f0b
--- /dev/null
+++ b/.changes/unreleased/Docs-20230525-103918.yaml
@@ -0,0 +1,6 @@
+kind: Docs
+body: add note before running integration tests
+time: 2023-05-25T10:39:18.75138+09:00
+custom:
+  Author: d-kaneshiro
+  Issue: nothing

From 3ed71b6d98918003c081825256eb0258df05ad6e Mon Sep 17 00:00:00 2001
From: Kshitij Aranke <kshitij.aranke@dbtlabs.com>
Date: Wed, 7 Jun 2023 09:30:00 -0700
Subject: [PATCH 3/3] Add space

---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 11568f6833f..e5a620e8bb9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -113,7 +113,7 @@ When installed in this way, any changes you make to your local copy of the sourc
 
 With your virtualenv activated, the `dbt` script should point back to the source code you've cloned on your machine. You can verify this by running `which dbt`. This command should show you a path to an executable in your virtualenv.
 
-Configure your [profile](https://docs.getdbt.com/docs/configure-your-profile) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate.Make sure to create a profile before running integration tests.
+Configure your [profile](https://docs.getdbt.com/docs/configure-your-profile) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate. Make sure to create a profile before running integration tests.
 
 ## Testing