feat!: Support workflow dispatch run details in response#4028
feat!: Support workflow dispatch run details in response#4028gmlewis merged 4 commits intogoogle:masterfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Nice, thanks for working on this - I saw the GitHub Changelog post about this yesterday and was planning to contribute this today but you beat me to it! I'm excited to remove our project's workaround for getting the run URL once this is merged and released! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4028 +/- ##
==========================================
+ Coverage 94.07% 94.10% +0.02%
==========================================
Files 207 207
Lines 19163 19207 +44
==========================================
+ Hits 18028 18074 +46
+ Misses 936 935 -1
+ Partials 199 198 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
gmlewis
left a comment
There was a problem hiding this comment.
Thank you, @LinaKACI-pro!
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.
cc: @stevehipwell - @alexandear - @zyfy29 - @Not-Dhananjay-Mishra
gmlewis
left a comment
There was a problem hiding this comment.
Excellent! Thank you, @LinaKACI-pro!
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.
cc: @stevehipwell - @alexandear - @zyfy29 - @Not-Dhananjay-Mishra
93acffe to
6817b9e
Compare
35e23b2 to
40a1676
Compare
|
No need to force push, just FYI. |
|
Thank you, everyone! |
|
Thank you everyone!🚀 |
|
@gmlewis Just curious - do you know when you'll cut a new release that includes this? |
We typically make releases about once per month (which would mean the next one is in about 3 weeks), but if people ask for a release earlier than that, we can usually accomodate such requests. Right now we have a bunch of PRs in-flight and it might be nice to get those in... feel free to help with code reviews if you have time, and please let me know if you need a release earlier than in 3 weeks. |
|
Sounds good! I'm definitely eager for this one but certainly understand waiting to get some other in-flight work across the finish line. Thanks for the answer! (and for all the hard work maintaining this library!) |
|
Yeah, I'm eager for this feature! It will make my proj way easier. Looking forward to it!!! |
OK, two requests sound good enough to me. I'll work on a release today or tomorrow after I take a look at what PRs are currently in-flight and hopefully close-to-merging. |
|
@rmacklin and @sunggun-yu - this is now released here: |
|
Awesome, thank you!! |
|
Thank you! |
BREAKING CHANGE:
CreateWorkflowDispatchEventByIDandCreateWorkflowDispatchEventByFileNamenow return*WorkflowDispatchRunDetails.Summary
Resolves #4027
ReturnRunDetailsfield toCreateWorkflowDispatchEventRequestto support the newreturn_run_detailsAPI parameterCreateWorkflowDispatchEventResponsestruct withWorkflowRunID,RunURL, andHTMLURLfieldsCreateWorkflowDispatchEventByIDandCreateWorkflowDispatchEventByFileNameto return(*CreateWorkflowDispatchEventResponse, *Response, error)instead of(*Response, error)ReturnRunDetails: true(200 OK with body) and omitted (204 No Content) casesBreaking change
The method signatures for
CreateWorkflowDispatchEventByIDandCreateWorkflowDispatchEventByFileNamechanged from returning(*Response, error)to(*CreateWorkflowDispatchEventResponse, *Response, error).API reference
https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#create-a-workflow-dispatch-event
Manual test
Tested against a real repository with a
workflow_dispatchworkflow using the following program:To reproduce, create a test program in a separate directory and use
go.modreplaceto point to the local changes:Then run:
Test program