Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

ref swagger-api/swagger-codegen/issues/9210 - update http urls to https #365

Merged
merged 1 commit into from
Apr 19, 2019

Conversation

frantuma
Copy link
Member

ref swagger-api/swagger-codegen/issues/9210 - update http urls to https

@frantuma frantuma merged commit 8d2b70d into master Apr 19, 2019
@frantuma frantuma deleted the ticket-9210 branch April 19, 2019 11:16
@JLLeitschuh
Copy link

This is an incomplete fix.

@frantuma
Copy link
Member Author

Thanks for reporting this, could you clarify what is missing? this addresses similar issues as those of swagger-api/swagger-codegen/issues/9210 fixed in swagger-api/swagger-codegen/pull/9389, but for codegen 3.0.0 branch.

@JLLeitschuh
Copy link

This does seem to fully resolve the issue:
swagger-api/swagger-codegen#9389

@frantuma
Copy link
Member Author

yes, that PR addresses the issues for master branch, while this PR addresses similar fix for the 3.0.0 branch

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants