Andrew Jones

@mattcollier sorry you had to change those consts but thanks for updating this.

@dlongley @mattcollier this can be closed correct? another PR added this feature I believe.

if I recall correctly this PR is not needed because it turns out the ed25519 keys use a common DER format that we already have a validator for. I believe...

Here are mine: ```bash update-s3-bucket: runs-on: ubuntu-latest steps: - name: 'S3 Bucket sync' uses: jakejarvis/s3-sync-action@master with: args: --acl public-read env: AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }} AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{...

did that now getting: AWS_ACCESS_KEY_ID is not set. Quitting. yeah this is weird. any idea why the secrets are not showing up? They are definitely set. ``` update-s3-bucket: runs-on: ubuntu-latest...

Thank you for the help. I was using environment secrets. I think the issue with those was that I was not telling it what environment to use. Using the repo...

``` The user-provided path ./reports does not exist. ``` I checked and I seem to be in an empty docker container, not sure how to get the dir that results...

I'm a total noob with github actions. Thanks for the help and it is working. Just updated my s3 bucket/ website with fresh reports for the w3c. Thanks for your...

@nadalin @David-Chadwick you might try using `@context` with back ticks in order to avoid pinging the github user with the name [context](https://github.com/context) who is not part of this issue. It...

the path can be set in the recorder's config object