withfig / fig

Public issue tracker for Fig.
https://fig.io
MIT License
2.05k stars 63 forks source link

fig issue title from cli doesn't carry over into github #1921

Open goleary opened 2 years ago

goleary commented 2 years ago

Checks

Operating system

windows

Expected behaviour

when i provide a title after using fig issue it should end up in github so I don't have to input it again.

Actual behaviour

no title carries over

Steps to reproduce

fig issue => write title => enter

Environment

fig-details:
  - cli-version: 1.5.0
  - desktop-version: 2.5.3
  - figterm-version: 5.2.0
hardware-info:
  - chip-id: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  - cores: 8
  - mem: 65198.25 GB
os-info:
  - Windows 10 Pro (or newer) - build 22621
environment:
  - shell: C:\Program Files\Git\usr\bin\bash.exe
  - terminal: vscode
  - cwd: C:\Users\olear\Documents\GitHub\upnext-firebase
  - exe-path: C:\Users\olear\AppData\Local\Fig\latest\fig.exe
  - install-method: unknown
  - env-vars:
    - DISPLAY: needs-to-be-defined
    - FIG_INTEGRATION_VERSION: 8
    - FIG_PID: 1957
    - FIG_TERM: 1
    - FIG_TERM_VERSION: 5.2.0
    - FIG_WORKFLOWS_KEYBIND: ^f
    - PATH: C:\Users\olear\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\olear\bin;C:\Program Files\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files\dotnet;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Users\olear\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files (x86)\Yarn\bin;C:\Program Files\Git\cmd;C:\Users\olear\AppData\Roaming\edgedb\bin;C:\Users\olear\scoop\shims;C:\Users\olear\AppData\Local\Microsoft\WindowsApps;C:\Users\olear\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\olear\AppData\Roaming\nvm;C:\Users\olear\AppData\Local\GitHubDesktop\bin;C:\Users\olear\AppData\Local\Android\Sdk\platform-tools;C:\Program Files\OpenSSL-Win64\bin;C:\Users\olear\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin;C:\Users\olear\cli;C:\Program Files\PostgreSQL\14\bin;C:\Users\olear\AppData\Local\Microsoft\WindowsApps;C:\Users\olear\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\olear\AppData\Local\ngrok;C:\Users\olear\AppData\Local\Programs\Python\Python310;C:\Users\olear\AppData\Local\Yarn\bin;C:\Users\olear\AppData\Local\Fig\latest;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl;C:\Users\olear\.local\bin;C:\Users\olear\.fig\bin        
    - SHELL: C:\Program Files\Git\usr\bin\bash.exe
    - TERM: xterm-256color
    - TERM_SESSION_ID: af529495-057a-4a11-978f-8f4689af044e
clo4 commented 2 years ago

I think this might be a Windows-specific bug - works fine for me on macOS