Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on GitHub action triggered by somebody else's repository

Post

GitHub action triggered by somebody else's repository

−0

Consider the following situation:

I have a GitHub repository for a LaTeX package: https://github.com/samcarter/beamertheme-spectrum
This LaTeX package depends on a class, for which somebody else has a GitHub repository: https://github.com/josephwright/ltx-talk

To make sure that my package stays compatible with the development of the class, I'd like to regularly run a GitHub Action in my repository to test this. At the moment, I run it on a schedule once a week:

name: Check with current ltx-talk

on:
  schedule:
    - cron: '47 13 * * 3'

Is it somehow possible to trigger this action based on events in the ltx-talk repository? For example every time a new version gets released or for every commit? I've read about repository_dispatch, but it seems this would require changes in the triggering repository.

In case it helps, I also have a fork of the ltx-talk repository, which is automatically kept up-to-date using Probot Pull.

github

posted 11 months ago

CC BY-SA 4.0

11mo ago

samcarter‭

186 reputation 5 3 30 13

Raw

Markdown

History

4 comment threads

Fork + repositorydispatch (4 comments)

What about git submodule? (5 comments)

Use a third service? (1 comment)

I also want this (4 comments)

matthewsnyder‭ wrote 11 months ago · edited 11 months ago

copy link

You could just run your own service on some other platform which monitors the upstream repo, and triggers the action of your own repo if any are detected. Even just a cron or systemd job on your laptop would work.

If there is a way to trigger from another directly, that would be interesting to know, but using a separate service to monitor seems easier in any case. All you need is:

Stateless script that checks upstream for new commits and triggers your repo if any are detected
Some way of running this script periodically

Plus you wouldn't be locked in to Github Actions or even Github. This approach will support any CI on any git host, you can even have one repo on gitlab and another on codeberg.

Communities

Comments on GitHub action triggered by somebody else's repository

GitHub action triggered by somebody else's repository

4 comment threads