Trigger downstream CI based on file change

[paulzierep]

I tried to set-up the CI jobs so that downstream workflows are executed based on file change.
E.g.: The filter communities workflow should be triggered when the all_tools.tsv file is changed, probably by the fetch_all_tools.yaml workflow, that is executed weekly.
But so far the workflow is not executed automatically. The workflow itself works fine, e.g. when triggered via the workflow_dispatch option, but it is not automatically triggered by file change.

[paulzierep]

@nsoranzo do you have an idea about this

[paulzierep]

Seems like one needs to specify a branch for this

  push:
    paths:
    - 'results/all_tools.tsv'
    branches: ["main"]

works

[paulzierep]

In fact, it does not work. It seems that CIs that interact with github and use the github_token as credentials do not subsequent actions.
https://github.com/orgs/community/discussions/25702
However, we can use the workflows_run event to get what we want https://stackoverflow.com/questions/62750603/github-actions-trigger-another-action-after-one-action-is-completed

I propose to trigger fetch_all_tools.yaml weekly and
the filter_communities.yaml as well as static.yml as subsequent workflows_run and
for each PR which changes data/communities (this will update the table and community results if a new community is added immediately)

[nsoranzo]

@paulzierep Did you have a look at #62 ?

[paulzierep]

Thanks @nsoranzo that should indeed also work !