Jason Kankiewicz
Jason Kankiewicz
Because there are no `git flow {bugfix,feature,hotfix,support} move ` or `git flow {bugfix,feature,hotfix,support} rename ` commands, one is forced to instead use the vanilla `git branch -m ` command which...
Being that there could be multiple support branches existing simultaneously along with the main branch, the `gitflow` command should enable one to switch from working on a bugfix/feature/release branch to...
The `git flow {bugfix,feature,hotfix} rebase` command enables one to rebase a branch on its basis branch but if the basis branch actually contains new commits and the branch has been...
Ideally every bugfix/feature branch should be based upon the develop branch but the `git flow {bugfix,feature} start ` command **does** support an optional `` argument for when it shouldn't. When...
Please add a `--base ` command line option to the `git flow {bugfix,feature} rebase` command so that an orphaned bugfix/feature branch can be conveniently rebased on develop—or another bugfix/feature branch—while...
The `git flow support publish ` subcommand doesn't exist and this is strange because a support branch has to be pushed to the origin repository in order for others to...
I've compensated for the removal of `AMsyncMessageChanges()` in PR #803 so that the automerge-c library's unit test suite will pass and it can therefore be re-enabled in the CI workflow.
@alexjg, I've finally exposed the Cursor API to C programs. In order to make the full unit test suite pass again, I also included the changes from PR #885 that...