-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the @actions/http-client
and @actions/github
modules for proxy support
#124
Conversation
Critical benefit of doing this is inheriting the proxy-honoring behavior from the @actions/http-client and @actions/github libraries
…e from api-client Also remove requestedDeployment field in favor of deploymentInfo.pending
…d one from api-client
…ne from api-client
@jeremy-daley-kr If you could verify the needed proxy support with this branch, that would be amazing! ❤️ uses: actions/deploy-pages@actions-http-client |
src/deployment.js
Outdated
core.info('Reported success!') | ||
core.setOutput('status', 'succeed') | ||
if (this.deploymentInfo) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is always truthy, thanks to line 57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So long as the methods are call in the intended order. 😅 Less of a concern for the status check but I picture a future where we invoke cancel()
potentially in a post-step if the workflow run fails or is canceled or something that may need to be able to operate without this.deploymentInfo
. We're not there today, though, so your point is definitely valid. 👍🏻
@JamesMGreene I'm getting this when I target your branch...
Update: I think that's what I was seeing when I first tried to go about this method, is that not all functions that have been added to octokit are available yet with the current version of |
@jeremy-daley-kr Ah, my bad. 🤦🏻♂️ I've updated to use |
@JamesMGreene Definitely getting there, but now I've got this: |
I think the page itself deployed. Maybe some optional chaining would get me further along to fill you in with more details? |
Thanks for the feedback, @jeremy-daley-kr! Sorry it didn't go smoothly. 😖 I'll find some time to do further testing on our side before I ask you to check again. 😅 |
No worries, man. I appreciate you sticking with it. I realize it's a bit harder to test if not behind a proxy yourself. If Github had a way of pairing, I'd just as soon do that. All I need to do at this point is just re-run the failed job since it pulls the latest from your branch, so just let me know. |
@jeremy-daley-kr Can you give this another try? I think I've worked out the kinks now. 🤞🏻 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just a few comments, but nothing blocking.
All Green on my end! Boom! 🤜💥🤛 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent work, and thank you!
@jeremy-daley-kr Awwwwwesome! 🎉 I'll work out the last few issues that my teammates have called out and try to get this shipped later today. 🚀 |
Was able to use this branch to successfully deploy all of our Pages starter workflow regression testing repos. 👍🏻 |
Published as part of the Any of the following
|
Fixes #112
Closes #128
Closes #111
Closes #106
Shout out to @daleyjem / @jeremy-daley-kr for reporting the issue, proposing a PR, discussing approaches, and hopefully also being up for testing this branch out...? 😁🤞🏻🙏🏻
TODO: