Missing documentation: corporate proxy and enterprise certificate configuration for GHE environments
@alexr00 ya está trabajando en esto.
Desde el 1/7/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Environment
- OS: Windows 11 Enterprise (corp-managed)
- VS Code: latest
- Extension: github.vscode-pull-request-github (latest)
- GitHub Enterprise Server or GitHub Enterprise Cloud
Description
The extension README and VS Code Marketplace page contain no documentation about how to configure the extension in corporate environments. Common enterprise setup requirements that are undocumented:
- Custom CA certificates — GHE instances often serve TLS certs signed by an internal CA. There is no guidance on using NODE_EXTRA_CA_CERTS or VS Code's http.systemCertificates setting with this extension.
- Proxy configuration — It is unclear whether the extension respects http.proxy in VS Code settings, HTTPS_PROXY env vars, or both. No troubleshooting guidance exists for ECONNREFUSED/CERT_UNTRUSTED errors on proxied networks.
- GHE SSL verification bypass for dev/staging — Some orgs use self-signed certs on non-prod GHE; the only workaround users currently find is NODE_TLS_REJECT_UNAUTHORIZED=0 which is unsafe.
- SSO token scope requirements — SAML-enforced organizations require PATs to be SSO-authorized; the extension does not guide users through this, leading to cryptic 403 errors.
Expected vs Actual Behavior
Expected: Wiki or README section covering: proxy settings, custom CA trust, SSO authorization steps, and known limitations for air-gapped GHE deployments.
Actual: No enterprise/corp configuration documentation exists; users must rely on community workarounds and trial-and-error.
Additional Context
This is a documentation gap, not a bug. A single 'Corporate / Enterprise Setup' section in the README would reduce a significant class of support requests from enterprise users.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.6k
- Forks
- 796
- Merge medio
- 14 h 34 min
- PR fusionados (30 d)
- 43
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/vscode-pull-request-github
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Issue 3 — Documentation Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
doesnt accept ghe signin Abierto
microsoft/vscode-pull-request-github#8982 · 1 asignado ·
-
microsoft/vscode-pull-request-github#8981 · 1 asignado ·
-
microsoft/vscode-pull-request-github#8980 · 1 asignado ·
Todos los issues de microsoft/vscode-pull-request-github
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
mksglu/context-mode#1200 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anthropics/claude-code#96687 ·
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
AOSSIE-Org/DebateAI#582 · 2 comentarios ·