Update default message for initialization of git repositories

0-bootstrap/README-Jenkins.md

@@ -179,7 +179,7 @@ You arrived to these instructions because you are using the `jenkins_bootstrap`
 
    ```bash
    git add .
-   git commit -m 'Your message - Bootstrap configuration using jenkins_module'
+   git commit -m 'Bootstrap configuration using jenkins_module'
    ```
 
 1. Push my-0-bootstrap branch to your repository YOUR_NEW_REPO-0-bootstrap with
@@ -241,7 +241,7 @@ You arrived to these instructions because you are using the `jenkins_bootstrap`
 
    ```bash
    git add backend.tf
-   git commit -m 'Your message - Terraform Backend configuration using GCS'
+   git commit -m 'Terraform Backend configuration using GCS'
    ```
 
 1. Push my-0-bootstrap branch to your repository YOUR_NEW_REPO-0-bootstrap with
@@ -369,7 +369,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize org repo'
    ```
 
 1. Push your plan branch.
@@ -458,7 +458,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize environments repo'
    ```
 
 1. Push your plan branch.
@@ -574,7 +574,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize networks repo'
    ```
 
 1. You must manually plan and apply the `shared` environment (only once) since the `development`, `non-production` and `production` environments depend on it.
@@ -727,7 +727,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize networks repo'
    ```
 
 1. You must manually plan and apply the `shared` environment (only once) since the `development`, `non-production` and `production` environments depend on it.
@@ -876,7 +876,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize projects repo'
    ```
 
 1. Also update `backend.tf` with your backend bucket from 0-bootstrap output.

0-bootstrap/README.md

@@ -223,7 +223,7 @@ your current Jenkins manager (controller) environment.
 
    ```bash
    git add .
-   git commit -m 'Initialize policy library'
+   git commit -m 'Initialize policy library repo'
    git push --set-upstream origin main
    ```
 
@@ -248,7 +248,7 @@ your current Jenkins manager (controller) environment.
    chmod 755 ./tf-wrapper.sh
 
    git add .
-   git commit -m 'Initialize bootstrap'
+   git commit -m 'Initialize bootstrap repo'
    git push --set-upstream origin plan
    ```
 

0-bootstrap/scripts/push-to-repo.sh

@@ -38,5 +38,5 @@ git config user.email "terraform-robot@example.com"
 git config user.name "TF Robot"
 git checkout main || git checkout -b main
 git add Dockerfile
-git commit -m "init tf dockerfile"
+git commit -m "Initialize tf dockerfile repo"
 git push origin main -f

1-org/README.md

@@ -167,7 +167,7 @@ Run `terraform output cloudbuild_project_id` in the `0-bootstrap` folder to see
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize org repo'
    ```
 
 1. Push your plan branch to trigger a plan for all environments. Because the

2-environments/README.md

@@ -117,7 +117,7 @@ commands. The `-T` flag is needed for Linux, but causes problems for MacOS.
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize environments repo'
    ```
 
 1. Push your plan branch to trigger a plan for all environments. Because the

3-networks-dual-svpc/README.md

@@ -185,7 +185,7 @@ If you are not able to use Dedicated or Partner Interconnect, you can also use a
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize networks repo'
    ```
 
 1. You must manually plan and apply the `shared` environment (only once) since the `development`, `non-production` and `production` environments depend on it.

3-networks-hub-and-spoke/README.md

@@ -188,7 +188,7 @@ If you are not able to use Dedicated or Partner Interconnect, you can also use a
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize networks repo'
    ```
 
 1. You must manually plan and apply the `shared` environment (only once) since the `development`, `non-production` and `production` environments depend on it.

4-projects/README.md

@@ -134,7 +134,7 @@ commands. The `-T` flag is needed for Linux, but causes problems for MacOS.
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize projects repo'
    ```
 
 1. You need to manually plan and apply only once the `business_unit_1/shared` and `business_unit_2/shared` environments since `development`, `non-production`, and `production` depend on them.

5-app-infra/README.md

@@ -104,7 +104,7 @@ commands. The `-T` flag is needed for Linux, but causes problems for MacOS.
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize policy library repo'
 
    git push --set-upstream origin main
    ```
@@ -153,7 +153,7 @@ commands. The `-T` flag is needed for Linux, but causes problems for MacOS.
 
    ```bash
    git add .
-   git commit -m 'Your message'
+   git commit -m 'Initialize bu1 example app repo'
    ```
 
 1. Push your plan branch to trigger a plan for all environments. Because the