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.
Post History
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 somebo...
#4: Post edited
- 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/).
- 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/).
#3: Post edited
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/).
#2: Post edited
- 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 there 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
- ```
- 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/
#1: Initial revision
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 there 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/
