I have found that it is difficult to reproduce old versions of quine-relay, even with the Dockerfile, because of unsupported Ubuntu versions and changing package versions. Even when I get it to work, it takes a very long time to run for all commits. The spoiler branch already has these build artifacts, so why doesn't it work? Well, it's force-pushed by GitHub Actions every time a change is pushed to master, so there is only the latest version.
With this PR, starting from now, updates to spoiler will simply push, so that the changes to spoiler can be tracked.
Since it was hard-coded to push to your repo, I made it work when run from a fork. Additionally, it will now have a more descriptive commit message and use the author information from the triggering commit and GitHub Actions as the committer.
You can see what this change looks like in the spoiler branch of my fork.
I have found that it is difficult to reproduce old versions of quine-relay, even with the Dockerfile, because of unsupported Ubuntu versions and changing package versions. Even when I get it to work, it takes a very long time to run for all commits. The spoiler branch already has these build artifacts, so why doesn't it work? Well, it's force-pushed by GitHub Actions every time a change is pushed to master, so there is only the latest version.
With this PR, starting from now, updates to spoiler will simply push, so that the changes to spoiler can be tracked.
Since it was hard-coded to push to your repo, I made it work when run from a fork. Additionally, it will now have a more descriptive commit message and use the author information from the triggering commit and GitHub Actions as the committer.
You can see what this change looks like in the spoiler branch of my fork.