release-0.10

release-0.10

This release allows you to specify the name of the test-script which is invoked by your Github Actions workflow file, which is useful because it allows you to run different testing-scripts on different events.

This was implemented in #8

release-0.9

release-0.9

This release updates our metadata-file, to correctly specify that we run via Docker.

release-0.8

release-0.8

This release updates the repository to contain a meta-data file, allowing the action to be listed upon the Github Actions marketplace.

There are no significant changes compared to the previous release.

release-0.7

This release updates the comments within our Docker entrypoint, entrypoint.sh, removing a redundant exit statement:

• #5 - exit $? in entrypoint.sh is misleading

release-0.6

This release features updated documentation, to cope with the fact that the Github Actions interface changed from using the HCL-language to a series of YAML files.

The changes were primarily contained in #3.

release-0.5

This release updates the README.md file to document how to run the tests on either:

• A new pull-request.
• A new commit.

Running the tests on both actions gives complete confidence that your project is never going to be in a broken state.

release-0.4

This is the initial public release of a simple action to run test-cases when pull-requests are opened, or updated.

If you create a shell-script .github/run-tests.sh inside your repository it will be executed every time a pull request is created/updated. As this is a shell-script you can do anything you wish. Typically we'd expect go test ./... or similar, but you have freedom to do almost anything.

release-0.3

This action is a general-purpose one, which is designed to allow you to run your project-specific tests when new pull-requests are submitted.

To keep things flexible the action runs .github/run-tests.sh from the root of your repository, allowing you to run arbitrary tasks. If the script exits cleanly that is regarded as a pass, otherwise a failure.