问如何在GitHub操作中使用env文件？

EN

      - name: 'Create env file'
        run: |
          touch .env
          echo API_ENDPOINT="https://xxx.execute-api.us-west-2.amazonaws.com" >> .env
          echo API_KEY=${{ secrets.API_KEY }} >> .env
          cat .env

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

- name: Do Something with env files
  env:
    QA_ENV_FILE: ${{ secrets.QA_ENV_FILE }}
    PROD_ENV_FILE: ${{ secrets.PROD_ENV_FILE }}
  run: |
    [ "$YOUR_ENVIRONMENT" = qa ] && echo $QA_ENV_FILE | base64 --decode > .env
    [ "$YOUR_ENVIRONMENT" = prod ] && echo $PROD_ENV_FILE | base64 --decode > .env

- There are some [ready-made actions](https://duckduckgo.com/?q=github+actions+dotenv&atb=v242-1&ia=web&iai=r1-1&page=1&sexp=%7B%22biaexp%22%3A%22b%22%2C%22msvrtexp%22%3A%22b%22%2C%22earlydeep%22%3A%22a%22%7D) that allow to read the `.env` variables (e.g. [Dotenv Action](https://github.com/marketplace/actions/dotenv-action),[Simple Dotenv](https://github.com/marketplace/actions/simple-dotenv)).

- You manually copy the content of the respective `.env`    files (say `.env.stage`, `.env.production`) into the respective GitHub Actions [secret variables](https://docs.github.com/en/actions/security-guides/encrypted-secrets) (say `WEBSITE_ENV_STAGE`, `WEBSITE_ENV_PRODUCTION`).

- Then at your GitHub Actions workflow script create the `.env` file from the desired variable like this `echo "${{secrets.WEBSITE_ENV_STAGE }}" > .env` and use it in the workflow.

- Now you use the GitHub Actions API to [create or update the secrets](https://docs.github.com/en/rest/reference/actions#create-or-update-a-repository-secret). On your local machine in the `dev` environment you write the NodeJS script that calls the API endpoint and write the `.env` files to the desired GitHub Actions secret variable (say as above into `WEBSITE_ENV_STAGE` or to both stage and production variables at once);