Example integration

[guzman-raphael]

Came across your solution in trying to find a way to share secrets in a safe way to fork contributors (for CI purposes). Would you mind sharing some example how I could incorporate this into an existing GitHub Actions CI workflow? Still relatively new to actions but solutions for secret access are few and far between. This looks promising!

[imjohnbo]

Hi @guzman-raphael! Sure – does this example and the workflows here help? 🙏

I think the problem is users might expect this to be a Action itself. It's not obvious from the readme that I have to copy the workflows into my own repo manually.

[guzman-raphael]

Thanks @imjohnbo @fidelcoria for the quick response. Coming from TravisCI and still getting the hang of how things operate in GH Actions. Looking forward to getting this working on a side project I have going on. :)

[guzman-raphael]

Hmmm, so it looks like I am having some issues trying to adopt this into a test project I've created here. I've created a PR from another user and when I trigger the PROW command, the action is triggered but I am getting an Error: HttpError: Not Found (see actions log) in the ok-to-test logs. Any ideas what could be wrong? I have created a GitHub app for authentication per the README.md. Also, referenced this. It has

• contents: rw
• metadata: r
• pull_requests: rw

[alzafacon]

Assuming secrets were added correctly (APP_ID, PRIVATE_KEY)
Maybe the app want installed correctly. https://github.com/guzman-raphael/github-actions-ci-poc/settings/installations
If your app doesn't appear on that page it's not installed on the repo.
Go to
https://github.com/settings/apps/GH_APP_NAME/installations
And install on the repo.

[guzman-raphael]

@fidelcoria-aa Thanks! We are getting closer! 😃. Did not realize that if I created a GitHub App that it still had to be manually installed. After doing this, it is triggering the expected ok-to-test-command action.

However, there is still a problem. It seems that on fork PR's, it is running integration.yml on a checkout of what is in the target branch as opposed to what is being supplied by the fork branch. Have a look at this new PR I created. Basically when parsing the results of the test, the modified secret display is not taking effect. Any thoughts why that could be?

BTW, many thanks guys. This is a pretty awesome workflow you've come up with!

[imjohnbo]

@guzman-raphael, are you checking out the merge commit?

BTW, many thanks guys. This is a pretty awesome workflow you've come up with!

🙇 🙏

[github-actions]

Beep boop! 🤖 This issue hasn't had any activity in a while. I'll close it if I don't hear back soon.