You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm trying to use an repository which receives the same event from different repositories. What I don't understand it's why it works with a repository (A) and it doesn't work if I've the same configuration in a repository (B).
This is my subtree repository on listen-dispatch.yml
This is what I've on my repositories which send the event to the previous one, there's one of them which works though there is another one which has the same configuration and share the access token from the same organization, both are private repositories.
# repository-dispatch.yml file on multiple repositories from the same organization which share the same PATname: trigger events in another repositoryon:
push:
branches: [ master ]jobs:
testing-trigger:
runs-on: self-hostedsteps:
- name: Repository Dispatchuses: peter-evans/repository-dispatch@v2.1.1with:
token: ${{ secrets.ACCESS_TOKEN }}repository: myorg/mysubtree-repoevent-type: update-subtree-repositoryclient-payload: '{ "repository": "${{ github.repository }}" }'# optional, default is {}
The text was updated successfully, but these errors were encountered:
It doesn't sound like you are doing anything wrong so I don't see any reason why it shouldn't work. If the access token is stored at the repository level, my only suggestion would be to double check it's correct by copy/pasting it again.
Hi, I'm trying to use an repository which receives the same event from different repositories. What I don't understand it's why it works with a repository (A) and it doesn't work if I've the same configuration in a repository (B).
This is my subtree repository on
listen-dispatch.yml
This is what I've on my repositories which send the event to the previous one, there's one of them which works though there is another one which has the same configuration and share the access token from the same organization, both are private repositories.
The text was updated successfully, but these errors were encountered: