Add note

README.md

@@ -14,3 +14,28 @@ bosh  create-release --force --tarball=/tmp/release.tgz
 # Upload release to bosh director
 bosh -e <bosh-env> upload-release /tmp/release.tgz
 ```
+
+
+# Release process
+
+## GitHub Credentials
+
+`release-please` requires a GitHub token to access the GitHub API. You configure this token via
+the `token` configuration option.
+
+> [!WARNING]  
+> If using GitHub Actions, you will need to specify a `token` for your workflows to run on
+> Release Please's releases and PRs.
+
+By default, Release Please uses the built-in `GITHUB_TOKEN` secret. However, all resources created
+by `release-please` (release tag or release pull request) will not trigger future GitHub actions workflows,
+and workflows normally triggered by `release.created` events will also not run.
+From GitHub's
+[docs](https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow):
+
+> When you use the repository's `GITHUB_TOKEN` to perform tasks, events triggered by the `GITHUB_TOKEN`
+> will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.
+
+You will want to configure a GitHub Actions secret with a
+[Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
+if you want GitHub Actions CI checks to run on Release Please PRs.