Siara

Hey @trivikr, thank you for opening this! I've reached out to a subject matter expert about this, and will keep you updated with what our next steps will be. 🚀

Hey @trivikr 👋 After talking with a subject matter expert, we've determined the best way to resolve this would be to update the example code in the doc you linked...

Hey @trivikr, I sent your question to our subject matter expert, and they are taking a look to get a better understanding of this. I do see what you are...

Hey @trivikr, I heard back from our subject matter expert and your proposed solution to update: `BRANCH=${{ github.ref }}` to `BRANCH="refs/pull/${{ github.event.pull_request.number }}/merge"` in the example is a great one....

Hey @krlmlr, thanks so much for catching that `github.path` was in the wrong place. ✨ This PR looks great to me, I'll go ahead and get it merged.

Hey @textbook, thank you so much for catching this and reporting the issue! And for your patience with us as we work through our backlog. 💛 We recently updated this...

Thank you so much for catching this @alanzirek! ⚡ You or anyone else is welcome to open a PR to update this image to show `v3` of the listed actions.

Thanks for opening this @jsoref, I definitely see how the way this note is phrased is confusing. You or anyone else is free to open a PR that updates the...

Hey @jsoref, thanks (again) for your patience with us as we work through all of the issues in our backlog. We appreciate it! 🙇‍♀ So I have been reading this...

@jsoref thanks for the quick response! ⚡ That part does make sense to me. In the documentation, it says that `GITHUB_ACTION_PATH` is "the path where an action is located." I...