Release file doesn't always open automatically

[Mrtenz]

A small UX improvement would be to open the release file using the editor of choice. We could have a simple config file in the user's home folder which stores the command to run to open the file, and call that when creating the release file.

[mcmire]

@Mrtenz Right now it checks for EDITOR and uses that first if it's defined:

create-release-branch/src/editor.ts

Line 27 in 99b81d7

const { EDITOR } = getEnvironmentVariables();

. Is that enough or do you feel like having a config file would be more reliable?

[mcmire]

Someone messaged me the other day and said that the tool didn't open an editor for them. They weren't using VSCode, they were using Cursor. So this is definitely still a problem.

We could support a config file, but I am not sure how many people would know about it. We could inform them about it as soon as the tool doesn't detect an editor. By then it would be a bit too late, they'd have to add the config file for next time, but that is definitely an option.

Alternatively, we could have the tool check for alternate editors — and do so by first checking for an executable, then a macOS app. We already check for the existence of code here but we could check for /Applications/Visual Studio Code.app/Contents/Resources/app/bin/code instead, and do a similar thing for Cursor. This way if the user has not installed the code executable it will continue to work.