With all of the GitHub Actions-related changes, it's become much easier to do integration testing of Restylers manifests. The setup-demo action in particular sets up all Restylers' test files so that the run action can be used normally and it runs over all test files. This was effectively what we've done as integration testing through the SDK before. Now, it's much lighter to do anywhere, we do it in the actions test suite and the Restyler test suite already; might as well do it here now.
The other responsibilities of promote were to move some files around on S3, which I re-write here as bin/promote. Now we don't rely on that executable of the SDK at all.
With all of the GitHub Actions-related changes, it's become much easier to do integration testing of Restylers manifests. The
setup-demoaction in particular sets up all Restylers' test files so that therunaction can be used normally and it runs over all test files. This was effectively what we've done as integration testing through the SDK before. Now, it's much lighter to do anywhere, we do it in the actions test suite and the Restyler test suite already; might as well do it here now.The other responsibilities of
promotewere to move some files around on S3, which I re-write here asbin/promote. Now we don't rely on that executable of the SDK at all.