Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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

+6
−0

Consider the following situation:


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.

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)
I also want this
Michael‭ wrote 11 months ago · edited 11 months ago

And here is a GitHub thread where I talk with some collaborators about running a cron that checks the other repo for updates to run our CI/CD steps.

TLDR: You could use the Atom feed of their commits to decide whether to do the rest of your steps.

samcarter‭ wrote 11 months ago

Thanks for the link!

Michael‭ wrote 11 months ago

Haha. You're going to be disappointed when you realize that the issue is still open because nobody did the work. 😅

samcarter‭ wrote 11 months ago

... but at least I no longer feel alone with this question :)