When finishing a GitFlow release in SourceGit and enabling the option to immediately push to the remote, the operation fails with a getopt parsing error.
The same release finish works correctly if the push step is skipped and executed manually afterwards.
Error output (git-flow-avh)
flags:WARN getopt: illegal option -- -
-p -u sh -- 2026-04-15
flags:FATAL unable to parse provided options with getopt.
Error output (git-flow-next)
Error: unknown flag: --push
Expected behavior
• Release should finish successfully
• Branches and tags should be pushed to remote when the option is enabled
Actual behavior
• Release finish fails when “push to remote” is enabled
• Works correctly without push
Environment
• OS: macOS (Apple Silicon)
• SourceGit version: 2026.08
• Git version: 2.53.0
• GitFlow: git-flow-avh (Homebrew)
• GitFlow: git-flow-next (Homebrew)
Analysis
SourceGit appears to append a --push flag to the git flow ... finish command when the “push to remote” option is enabled.
However:
• git-flow-avh fails with a getopt parsing error
• git-flow-next explicitly reports --push as an unknown flag
This indicates that:
• --push is not a valid or consistently supported flag for git flow release finish
• SourceGit is constructing an invalid command when push is enabled
Steps to reproduce
1. Start a GitFlow release
2. Finish the release in SourceGit
3. Enable “push to remote”
4. Execute
Workaround
• Disable push in SourceGit
• Push manually after finishing the release
Notes
Notes
The argument sequence in the first error output (-p -u sh -- ) suggests that parameters are incorrectly constructed or passed to the underlying GitFlow command.
Additionally, since git-flow-next does not support --push, the issue appears to be a mismatch between SourceGit’s expected CLI interface and the actual GitFlow implementations.
When finishing a GitFlow release in SourceGit and enabling the option to immediately push to the remote, the operation fails with a getopt parsing error.
The same release finish works correctly if the push step is skipped and executed manually afterwards.
Error output (git-flow-avh)
Error output (git-flow-next)
Expected behavior
• Release should finish successfully
• Branches and tags should be pushed to remote when the option is enabled
Actual behavior
• Release finish fails when “push to remote” is enabled
• Works correctly without push
Environment
• OS: macOS (Apple Silicon)
• SourceGit version: 2026.08
• Git version: 2.53.0
• GitFlow: git-flow-avh (Homebrew)
• GitFlow: git-flow-next (Homebrew)
Analysis
SourceGit appears to append a --push flag to the git flow ... finish command when the “push to remote” option is enabled.
However:
• git-flow-avh fails with a getopt parsing error
• git-flow-next explicitly reports --push as an unknown flag
This indicates that:
• --push is not a valid or consistently supported flag for git flow release finish
• SourceGit is constructing an invalid command when push is enabled
Steps to reproduce
1. Start a GitFlow release
2. Finish the release in SourceGit
3. Enable “push to remote”
4. Execute
Workaround
• Disable push in SourceGit
• Push manually after finishing the release
Notes
Notes
The argument sequence in the first error output (-p -u sh -- ) suggests that parameters are incorrectly constructed or passed to the underlying GitFlow command.
Additionally, since git-flow-next does not support --push, the issue appears to be a mismatch between SourceGit’s expected CLI interface and the actual GitFlow implementations.