random fixes

Author: sg

.github/workflows/cdk-deploy.yml .github/workflows/cdk-deploy-dev.yml

@@ -1,4 +1,4 @@
-name: Manually Deploy a CDK stack with OIDC
+name: Deploy a CDK stack to dev env with OIDC
 
 on:
   workflow_dispatch:

.gitignore

@@ -1,4 +1,4 @@
-*.js
+.*.js
 !jest.config.js
 *.d.ts
 node_modules

README.md

@@ -13,19 +13,19 @@ These instructions will get you a copy of this project up and running in your ow
 - Create a repo for this project.
 - Setup Github environments and secrets in the repo you just created. Use SECRETS, not variables.
 - Add repositories you want to grant deployment permissions to the `github-actions-role-stack.ts` file.
-- Bootstrap the project with cdk deploy --all.
+- Bootstrap the project with cdk deploy --all for every aws account you plan to deploy to.
 - Configure the actions workflow to suit your needs.
 - Add new projects to the `github-actions-role-stack.ts` file as needed.
 
 ### Setup Github Environments and Secrets
 
 1. Create an environment in your Github repository settings.
-   - Name the environment based on where it is deploying. (ie prod, dev, staging, etc based on your needs.)
+   - Name the environment based on where it is deploying. (ie prod, dev, staging, etc. based on your needs.)
    - The default is the main branch is prod.
 2. Create secret variables in each Github environment you are deploying too. USE SECRETS, NOT variables.
    - `AWS_ACCOUNT_ID`: The AWS account ID where the CDK application will be deployed. (Your AWS account number)
    - `AWS_REGION`: The AWS region where the CDK application will be deployed. (us-east-1)
-   - `ENVIRONMENT`: The name of the deployment environment. Default is main branch is prod. (ie prod, dev, staging, etc)
+   - `ENVIRONMENT`: The name of the deployment environment. Default is main branch is prod. (ie prod, dev, staging, etc.)
 
 ### Add Repositories you want to grant deployment permissions to