Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35011
b7bf7fba fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Canceled
35011
96a47107 fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Canceled
35011
dfc4e82b fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Succeeded
35011
b3773b5a fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Succeeded
35011
d0c82ce9 fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Canceled
35011
04af85fe fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Succeeded
35011
4d0546e2 fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Succeeded
35011
e9d63edb fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Canceled
35011
49c16013 fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu
Canceled
35011
ed915179 fix(core): add timeouts to GitHub push flow to prevent CLI hangs ## Current Behavior The `pushToGitHub` flow calls `gh api user` and `gh repo create --push` with no timeout via `spawnAndWait()`/`execAndWait()`. When gh CLI is wrapped by 1Password SSH agent, credential managers with GUI prompts, SSH keys with passphrases, or corporate SSO, these calls hang indefinitely—freezing the CLI after workspace creation with no indication of what's happening. YTD data shows a 96.3% failure rate (16,426 failures out of 17,058 attempts). ## Expected Behavior - The initial `gh` auth check (`gh api user`) has a 2-second timeout. If gh is slow to respond (hung on credential prompt), the push flow is skipped gracefully instead of freezing. - The `gh repo create --push` command has a 60-second timeout. If the push hangs, the process is killed and a helpful message is shown. - If `gh` CLI is not installed, the push flow is skipped immediately without attempting any network calls. - Error messages now include actionable fallback: "You can push manually with: git push -u origin main". ## Related Issue(s) Fixes NXC-4141
by Jack Hsu