Are there a breaking changes

[Serhioromano]

Hello,

I am maintainer for serhioromano.vscode-gitflow

It used to work with git-flow or gitflow-avh. Those projects long not supported but it worked. now one of my useres pointed me to your direction. I would like to update my extension to use your projects. Are there breaking changes? Commands looks the same, but output? I relay on come commands output to confirm results.

[alexrinass]

Hi! Thanks for reaching out — glad to hear about your interest in supporting git-flow-next.

Commands: We aim to be command-compatible with git-flow-avh, so existing command invocations should work as-is. We also support importing legacy configurations.

Output: We can't yet guarantee output compatibility. This is something we want to address, but it requires building a structured test suite that captures and compares output across common scenarios.

A few things we're considering for the roadmap:

• An output compatibility flag that reproduces legacy output and exit codes
• A machine-readable output mode (e.g. --format=json) that tools like yours could reliably parse
• Structured exit codes for reliable error handling

Could you share examples of specific command output your extension parses? That would help us prioritize compatibility for the most common integration points.

EDIT: I noticed that we have a compatibility report here, but to mainly covers the command calling part.

[Serhioromano]

Thank you for extended answer.

For instance

let b = this.util.execSync(`${this.util.flowPath} config list`).replace("\r", "").split("\n");
this.branches.master = b[0].split(": ")[1].trim();
this.branches.develop = b[1].split(": ")[1].trim();
this.branches.feature = b[2].split(": ")[1].trim();
this.branches.bugfix = b[3].split(": ")[1].trim();
this.branches.release = b[4].split(": ")[1].trim();
this.branches.hotfix = b[5].split(": ")[1].trim();
this.branches.support = b[6].split(": ")[1].trim();

This is how I parse names of branches. So if your app return same test, name of branches in the same order without description text in first line that would match.

The offer to create a JSON output format is great.

Also something like git flow next that return success is also good to define that your package is installed. Sort of health request.

If you consider to create json as output format, I could clone my extension, rename to Gin Flow Next and offer it as a companion to your particular project, and even figure out way to install this with extension itself to avoid complications for end users.