Add cautionary "notes"

bamboo/2-audit.md

@@ -31,6 +31,7 @@ You will audit the configured Bamboo pipelines. Answer the following questions b
     ```bash
     gh actions-importer audit bamboo -o tmp/audit --config-file-path bamboo/bootstrap/config.yml
     ```
+    > Note: The `--config-file-path` option is not required and is used throughout these labs to convert files that are stored locally for this lab. When performing a migration on your own Bamboo Server, `config-file-path` can be omitted and GitHub Actions Importer will programmatically fetch pipelines using the Bambooo REST APIs.
 
 3. The command will list all the files written to disk in green when the command succeeds.
 

bamboo/3-dry-run.md

@@ -34,6 +34,7 @@ You will be performing a dry run against a single Bamboo pipeline. Answer the fo
     ```bash
     gh actions-importer dry-run bamboo build --source-file-path bamboo/bootstrap/source_files/bamboo/bamboo.yml -p MARS-ROCKET --output-dir tmp/dry-run
     ```
+    > Note: The `--source-file-path` option is not required and is used throughout this lab to convert a pipeline that is stored locally. This can be omitted and GitHub Actions Importer will programmatically fetch pipelines using the Bamboo REST APIs
 
 3. The command will list all the files written to disk when the command succeeds.
 

bamboo/4-migrate.md

@@ -29,6 +29,8 @@ Answer the following questions before running a `migrate` command:
     $ gh actions-importer migrate bamboo build --target-url <target_url> --output-dir tmp/migrate --source-file-path bamboo/bootstrap/source_files/bamboo/bamboo.yml
     ```
 
+    Note: The `--source-file-path` option is not required and is used throughout this lab to convert files that are stored locally. This can be omitted and GitHub Actions Importer will programmatically fetch pipeline definitions using the Bamboo REST APIs.
+
 2. The command will write the URL to the pull request that is created when the command succeeds.