editor is not taking account with command glab issue note

Checklist

  • I'm using the latest version of the extension (Run glab --version)
    • Extension version: glab version 1.41.0 (2024-05-28)
  • Operating system and version: Windows 11 (10.0.22631)
  • Gitlab.com or self-managed instance? blade-group.com instance
  • GitLab version (if self-managed) {"version":"17.1.0-pre","revision":"163f9ba30e9","kas":{"enabled":true,"externalUrl":"wss://kas.gitlab.com","version":"17.1.0-rc9"},"enterprise":true}
  • I have performed glab auth status to check for authentication issues

Summary

editor in config file is not used with glab issue note command but works with glab issue create

Environment

  • OS: Windows
  • SHELL: cmd (with clink)
  • TERM: Windows Terminal
  • GLAB: glab version 1.41.0 (2024-05-28)

Other:

Steps to reproduce

  • set a new editor in config file (I try both local and global config).
  • try to create a new issue with glab issue create. It works, great!
  • try to add a new note to an issue with glab issue note. Open Windows notepad (🤮).

What is the current bug behavior?

editor config is not used for certain commands (glab issue note)

What is the expected correct behavior?

glab should always use editor in config file to write text.

Relevant logs and/or screenshots

Possible fixes

I can fix the bug using variable environnement but I would prefer that my config file works great.

Edited Jun 10, 2024 by Paul Corbineau
Assignee Loading
Time tracking Loading