I have the following use case:
Let’s say I have 2 repositories A and B. A is a software package and B is an extra tutorial containing some not so common use cases of that software package, both owned by me and public.
I have Travis-CI currently running on A but not B. Is it possible to use Github Action to trigger Travis-CI in B (something like this, new commit in A will trigger a sending of message “commit” in B so Travis will run in B everytime I have new commit in A). So I can just put some critical tests in A travis-ci but also make sure the tutorial run fine in B.