All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Issue #11 Added ability to configure if feature base branches are automatically pushed to origin after finishing and merging them
- Merged Pull Request for Issue #17. Fix for allowing dot '.' in git branch name path as long as it is not the beginning of the path. Thanks to Vasily Pikulev
- Upgraded TypeScript compilation to task version 2.0.0 per VS Code authors' request
- Issue #12 Fixed hotfix branches not being merged in to master when finished
- Issue #7 Ability to switch applications while input box is shown and not having it disappear
- Issue #10 Fixed when naming a branch with spaces caused bad merging in to develop instead of defined base branch
- Issue #6 New configuration value, showStatusBarFinisher. Defaulted to true, set to false to not show the new "Finish" status bar button introduced in 1.2.0 release. Given that there may be many extensions installed that utilize the status bar, it can become quite crowded, this allows you to make it a little less so if you find the button not really needed in your set up.
- New statusbar button to quickly finish features, releases, or hotfixes
- New keyboard shortcuts for quickly running commands
- New configuration value, askBeforeDeletion. When finishing a feature, release, and/or hotfix, you will now be asked if you would like to delete the branch (only local not remote if you have pushed it). Setting is true by default. If you set to false, it will follow the behavior of the deleteBranch setting.
- New configuration value, deleteBranchByDefault. When finishing a feature, release, and/or hotfix, this setting will determine if the branch is deleted by default or not. Setting is false by default. If you set to true, and askBeforeDeletion is set to false, then branches will be deleted without question.
- In support of the new statusbar button, the command menu structure had to be changed somewhat. Starting & Finishing features, releases, and/or hotfixes commands are now listed on the command menu (Cmd+P/Ctrl+P), as are Initialize and Git Status.
- Issue #3 Ability to create release and/or hotfix branches based on branches other than default branch ("development" and "production" respectively)
- Issue #3 Ability to now create feature branches based on branches other than "development" branch, prior release only allowed to create features off of either development or another "feature"
- Ability to create feature branches based on branches other than "development" branch
- Edited the README.md to be more robust on how to use the extension
- Error when finishing Release or Hotfix with tagging
- Ability to initialize git flow repository settings using custom values
- Ability to initialize git flow repository settings
- Removed need for gitflow or gitflow-avh to be installed prior to using the extension. All commands now run organic git commands
- Issue #1 Error that occurred when trying to use the extension that claimed there wasn't a git repo in the current or any parent folder
- This CHANGELOG file.
- Updated README file.
- Updated package.json to add keywords and badges
- Hotfixes require a TAG to be defined, but extension didn't support it, thus it wouldn't finish releases
- Releases require a TAG to be defined, but extension didn't support it, thus it wouldn't finish releases
- Functionality to check for illegal characters in branch names
- How git directory is found. No longer need to have code file open
- First version of extension
- Allowed for creation of features, releases, hotfixes
- Functionality to convert spaces to _ in branch names