← Back to issue list

Opt-in configuration to always use git+ssh for remote builds

View original Github issue

Metadata

Project
craft-application
Number
#793
Type
issue
State
open
Author
lengau
Labels
Status: Triaged Type: Enhancement
Created
Updated
Closed
—

Current evaluation

Triaged enhancement to add opt-in configuration forcing git+ssh for remote builds; public projects still use HTTPS, while private projects use SSH.

Suggested action: keep open

Reason: The issue is explicitly labeled "Status: Triaged" and was opened by maintainer lengau. The current code confirms the behavior: remote-build pushes use SSH only for private projects and HTTPS otherwise; the remaining ambiguity is the configuration name and whether the option should affect both push and recipe URLs, so it remains a valid open enhancement rather than a stale issue.

Evaluated by: mr-cal-bot

Impact: 42 Quick Win: 20 Complexity: 38 Confidence: 91 Actionability: 78

Issue body

### What needs to get done Currently we use HTTPS uploads for remote builds unless we're on a private project, but users should have a way to opt into using SSH always. ### Why it needs to get done Git over SSH is more reliable.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 42
Quick Win: 20
Complexity: 38
Confidence: 91
Actionability: 78
keep open Triaged enhancement to add opt-in configuration forcing git+ssh for remote builds; public projects still use HTTPS, while private projects use SSH.
stealth/space-bunny-alpha
Impact: 45
Quick Win: 21
Complexity: 40
Confidence: 88
Actionability: 76
keep open Maintainer-triaged enhancement to add an opt-in mode that forces git-over-SSH for remote-build uploads instead of HTTPS for public projects; it remains open with no resolving commit identified.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 22
Complexity: 25
Confidence: 75
Actionability: 75
keep open Enhancement to add opt-in configuration for always using git+ssh for remote builds instead of HTTPS for public repositories.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19
Staleness: 62
Complexity: 45
Confidence: 80
Support Request: 5
keep open Enhancement to add an opt-in config for always using git+ssh in remote builds instead of HTTPS for public repos. Triaged by maintainer, no implementation yet; code still uses HTTPS for public repos.
qwen/qwen3.6-35b-a3b
Staleness: 80
Complexity: 20
Confidence: 80
Support Request: 0
keep open Enhancement to add an opt-in configuration for using git+ssh instead of HTTPS for remote builds. Triaged by a maintainer but inactive for over a year with no implementation progress or discussion.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 80
Support Request: 0
close stale Enhancement requesting an opt-in configuration to use git+ssh for remote builds instead of HTTPS. Triaged but inactive for over a year with no maintainer follow-up or implementation progress.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.