github-actions
Github Actions – trigger another action after one action is completed
There are 2 options of doing this: Use a second job inside the same workflow.yml together with the needs keyword Create a separate notify.yml workflow that uses the workflow_run event as a trigger 1. Same workflow, separate job with needs keyword In your workflow.yml file you simply define two jobs like this (leveraging the needs: … Read more
Github actions share workspace/artifacts between jobs?
You can use the Github Actions upload-artifact and download-artifact to share data between jobs. In job1: steps: – uses: actions/checkout@v1 – run: mkdir -p path/to/artifact – run: echo hello > path/to/artifact/world.txt – uses: actions/upload-artifact@master with: name: my-artifact path: path/to/artifact And job2: steps: – uses: actions/checkout@master – uses: actions/download-artifact@master with: name: my-artifact path: path/to/artifact – run: … Read more
The unauthenticated git protocol on port 9418 is no longer supported
First, this error message is indeed expected on Jan. 11th, 2022. See “Improving Git protocol security on GitHub“. January 11, 2022 Final brownout. This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol. This will help clients discover any lingering … Read more
How do I use an env file with GitHub Actions?
a quick solution here could be having a step to manually create the .env file before you need it. – 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