Use comment trigger to run acceptance tests for PRs. #929
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates our acceptance testing strategy from using GitHub environments to a comment trigger. It leverages the
peter-evans/slash-command-dispatch
action to fire arepository_dispatch
. The action handles parsing arguments and checking the required permissions of the reviewer.To trigger a run of the acceptance tests for a PR, you may use the
/testacc
in a comment. Thepkg
andsha
arguments are required. This allows us to limit the packages being tested for quick feedback and protect against timing attacks. For example, to run the acceptance tests for thedroplet
package, the command may look like:To run the entire suite, use
pkg=digitalocean
.You can find an example in my fork: andrewsomething#6
Somethings to note:
Additionally, this:
CONTRIBUTING.md
file and moves the existing README content that is not user-focused into it.