You just need to load your variables into the github virtual environment.  e.g. export in whatever languages/tools of your choices.  e.g. dotenv for javascript or in bash just _export $(<.env) _inside one of your steps. (as long as they are in the same job they will be in the same environment).

Hello @anthonywc.   How do I get the file with my environment variables into the virtual environment if it’s not in the repository?  The file has API keys that I don’t want to add to the repository.  Thank you.

Thank you @smscodeverification for answing my question even it it was not he answer I wanted to hear.  Also thnk you letting me know about the upcoming API.  All the best.

You can store your secrets inside repository encrypted with ‘gpg’ tool and decrypt them as a step in workflow job

a similar solution is described here https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#limits-for-secrets

Any updates on this issue?

Can’t we store content of .env file in a secret variable ENV_FILE and then create a step to create .env file from secrets,

- name: Create .env file
   run:  echo "${{ secrets.ENV_FILE }}" > .env

Then may be delete .env file later

Any Update on this issue?