Add the list of required secrets to CI readme

.github/workflows/nightly-prs-to-main.yml

@@ -19,4 +19,3 @@ jobs:
  secrets:
  token: ${{ secrets.ACCESS_TOKEN }}
  asset-keys: '{"TestResourceKey": "${{ secrets.SUPER_RESOURCE_KEY}}"}'
-

.github/workflows/nightly-publish-main.yml

@@ -20,4 +20,3 @@ jobs:
  secrets:
  token: ${{ secrets.ACCESS_TOKEN }}
  asset-keys: '{"TestResourceKey": "${{ secrets.SUPER_RESOURCE_KEY}}", "PypiToken": "${{ secrets.PYPI_TOKEN }}"}'
-

ci/README.md

@@ -1,2 +1,10 @@
 # API Specific CI/CD Approach
-This API complies with the `common-ci` approach.
+This API complies with the `common-ci` approach.
+
+The following secrets are required:
+* `ACCESS_TOKEN` - GitHub [access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#about-personal-access-tokens) for cloning repos, creating PRs, etc.
+ * Example: `github_pat_l0ng_r4nd0m_s7r1ng`
+* `SUPER_RESOURCE_KEY` - [resource key](https://51degrees.com/documentation/4.4/_info__resource_keys.html) for integration tests
+ * Example: `R4nd0m-S7r1ng`
+* `PYPI_TOKEN` - [PyPI token](https://pypi.org/help/#apitoken) for publishing packages
+ * Example: `pypi-sUp3r-l0nG_r4nd0m-s7r1Ng`