![]() ![]() The only incorrect part is the commit (my master commit instead of actual PR commit ( pull_)), I have that information to provide the action with. The deployment options are still valid, the project activity log can be viewed to see that a new deployment is added, and a CLI API query lists the deployment description. This action may benefit from a similar pr_number feature? The only feature I am losing with my setup with workflow_run is the deployment status updates on the pull request, but the PR comment fulfills the same purpose. Personally I don’t need this feature, but it might be beneficial to other users of your action? ($) is ready! :tada:īy providing the PR number (transferred via artifact), I am able to get my comments updated again. For programming actions, GitHub Actions supports C, C++, C, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. It has a number option to provide PR number (used if no pull_request event is found): - uses: preview ![]() I use a different action to manage the PR comments. This adds a deployment comment on a commit that is relevant to the pull request. enable-commit-comment appears to be working, but it is taking the commit/SHA from my master branch that the workflow_run is running from as it’s not aware of my pull request anymore. ![]() At HashiCorp, where I currently work on the Digital Team, we’ve leveraged GitHub actions to build out our ETL pipline for ingesting versioned docs content for our various products' documentation sites waypointproject.io, vaultproject.io are a couple. The action is no longer able to add a comment, deployment environment status, check suite status (enable-commit-status), etc. See docs for note on environment variable and github context equivalents. I am providing the secrets to deploy, the build directory to publish and other field values that I can, this all works as expected. To get this action to work with non-collaborator PRs I am following the advice to move job steps that require secrets into a separate workflow_run workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |