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.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post 11 months ago by Karl Knechtel‭.

43 / 255
  • Github action triggered by somebody else's repository
  • GitHub action triggered by somebody else's repository
  • 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:
  • https://github.com/samcarter/beamertheme-spectrum/blob/main/.github/workflows/Check-ltx-talk.yaml
  • ```
  • 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 https://probot.github.io/apps/pull/
  • 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](https://github.com/samcarter/beamertheme-spectrum/blob/main/.github/workflows/Check-ltx-talk.yaml):
  • ```yml
  • 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](https://probot.github.io/apps/pull/).

Suggested 11 months ago by Michael‭