Allow request an insecure gitea server #18
No reviewers
Labels
No Label
kind
bug
kind
build
kind/compatible
kind
dependencies
kind
docs
kind
enhancement
kind
feature
kind
help wanted
kind
proposal
kind
refactor
related
act
related
environment
related
exec
related
gitea
related
workflow
reviewed
confirmed
reviewed
duplicate
reviewed
invalid
reviewed
needs feedback
reviewed
wontfix
reviewed
workaround
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/act_runner#18
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "lunny/act_runner:lunny/allow_insecure_opt"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When deploy a Gitea server with a self-signed HTTPS certification. Runner will be failed when connect to Gitea server. This PR will fix that to allow ignore the HTTPS certification verification.
@lunny You fell into the same trap like me, using such an empty http transport would make http proxies unusable in insecure mode.
See the http transport code of my act_runner for GitHub
a52520733e (diff-7a224f301a89d8716007002cfadb0d63b44e08506273e180f8947ad11a624cb4R153)
@lunny can you please add a description to this pull request?