Add additional secrets to README

Included a step for adding global enroll secret and ensuring that secrets are set for all environment variables referenced in configuration

README.md

@@ -14,8 +14,10 @@ How to set up your GitOps workflow:
 
 5. Add `FLEET_URL` and `FLEET_API_TOKEN` secrets to your new repository's secrets. Learn how [here](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository). Set `FLEET_URL` to your Fleet instance's URL (ex. https://organization.fleet.com). Set `FLEET_API_TOKEN` to an API token for an API-only user in Fleet. Learn how [here](https://fleetdm.com/docs/using-fleet/fleetctl-cli#create-api-only-user).
 
-6. Push your cloned and modified code to your repo.
+6. Add secrets to your repository as well as 'workflow.yml' for `FLEET_GLOBAL_ENROLL_SECRET` and for all environment variables that are mentioned in the global/team YAML files.
 
-7. In GitHub, enable the `Apply latest configuration to Fleet` GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.
+8. Push your cloned and modified code to your repo.
+
+9. In GitHub, enable the `Apply latest configuration to Fleet` GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.
 
 For all configuration options, go to [GitOps reference](https://fleetdm.com/docs/using-fleet/gitops) in the Fleet documentation.