Hello,
I developed an API client based from an OpenAPI file, and it use your action to open PR when the OpenAPI is updated (in order to update the client). Great work on this action BTW ! 🎉
I want to launch the build pipeline when the PR is created. So I have looked at your documentation and choose to use SSH Deploy key. It's a convenient solution because the repo is part of organization, so I don't want to use a PAT since I will not be able to review the PR then !
However, the build workflow doesn't trigger, even with SSH deploy key.
Could you help me to sort this out please ?
Here is the update workflow (which create the PR) : https://gist.github.com/QuentinLemCode/ee9ae0ea01cd26d96bb7081e6a27254a
And here is the build workflow : https://gist.github.com/QuentinLemCode/b0621d9cd2bb82905eea4f37a53458b7
I have already double-checked that the secret and the deploy key is well configured in Github GUI (it even says that the key has been used).
Thanks !
Hello,
I developed an API client based from an OpenAPI file, and it use your action to open PR when the OpenAPI is updated (in order to update the client). Great work on this action BTW ! 🎉
I want to launch the build pipeline when the PR is created. So I have looked at your documentation and choose to use SSH Deploy key. It's a convenient solution because the repo is part of organization, so I don't want to use a PAT since I will not be able to review the PR then !
However, the build workflow doesn't trigger, even with SSH deploy key.
Could you help me to sort this out please ?
Here is the update workflow (which create the PR) : https://gist.github.com/QuentinLemCode/ee9ae0ea01cd26d96bb7081e6a27254a
And here is the build workflow : https://gist.github.com/QuentinLemCode/b0621d9cd2bb82905eea4f37a53458b7
I have already double-checked that the secret and the deploy key is well configured in Github GUI (it even says that the key has been used).
Thanks !