-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repo dispatch #18
Repo dispatch #18
Conversation
7d02e08
to
611b992
Compare
611b992
to
ba24f61
Compare
I don't understand every line, but I get the gist of it. Looks good. |
Example of issue created ome/omero-ms-zarr#98. The issue was created even on success during the test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few minor, mostly style and comprehension comments. Otherwise, looks good.
@joshmoore I have re-used the name and review the explanation. It will be good to have that in place so we can evaluate it with the coming merge of ome-zarr-py PRs |
Merging so we can test with the upcoming ome-zarr-py PRs |
The proposed changes allow to trigger a job in this repository when a PR is merged in one of the "upstream" repositories that the test_suite covers e.g. ome-zarr-py
It uses the repository dispatch event.
run_test_suite
is posted by the upstream repo when a PR is merged