git-flower issueshttps://staging.gitlab.com/alexwilkinson/git-flower/-/issues2017-07-15T02:48:30Zhttps://staging.gitlab.com/alexwilkinson/git-flower/-/issues/9Shell Out Directly To Git Instead of Using Git Gem2017-07-15T02:48:30Zusername-removed-889669Shell Out Directly To Git Instead of Using Git GemThe Git gem was a great way to write these scripts very quickly, but now that I've wrapped the scripts in this gem and am trying to test everything in a minimally brittle way, the gem is getting in the way. [This article](https://www.set...The Git gem was a great way to write these scripts very quickly, but now that I've wrapped the scripts in this gem and am trying to test everything in a minimally brittle way, the gem is getting in the way. [This article](https://www.sethvargo.com/unit-and-functional-testing-git-with-rspec/) demonstrates a very straightforward way to mock calls out to `git` in unit tests that trump what would I have to do to test `GitRepository`, which is basically just use `receive_message_chain`. I'd rather test the use of git commands instead of the use of ruby methods on a wrapper for Git.
This probably wouldn't be too difficult to pull off because I've isolated use of the gem to `GitRepository`, but it's not a huge priority.https://staging.gitlab.com/alexwilkinson/git-flower/-/issues/8Create A Project Config2017-07-14T19:22:11Zusername-removed-889669Create A Project ConfigWe need a place to configure simple settings like git-flow config (see #7) and more complicated scenarios like project manager integration in the future. Maybe just a `.git_flower.yml` file.We need a place to configure simple settings like git-flow config (see #7) and more complicated scenarios like project manager integration in the future. Maybe just a `.git_flower.yml` file.https://staging.gitlab.com/alexwilkinson/git-flower/-/issues/7Permit Multiple Hotfixes2017-07-14T19:22:10Zusername-removed-889669Permit Multiple HotfixesShould add some kind of configuration for honoring the `git flow config set allowmultihotfix true` setting for `git-flow-avh`. This will require having some kind of configuration ability in the first place, so blocked by #8.Should add some kind of configuration for honoring the `git flow config set allowmultihotfix true` setting for `git-flow-avh`. This will require having some kind of configuration ability in the first place, so blocked by #8.https://staging.gitlab.com/alexwilkinson/git-flower/-/issues/6Add Finish Commands2017-07-13T03:35:04Zusername-removed-889669Add Finish CommandsWould be great for GitFlower to have its equivalents of `git flow hotfix finish [NAME]` and `git flow feature finish [NAME]` that not only removes the branch and merges into develop or master, but can also delete the origin version of th...Would be great for GitFlower to have its equivalents of `git flow hotfix finish [NAME]` and `git flow feature finish [NAME]` that not only removes the branch and merges into develop or master, but can also delete the origin version of the branch (since git-flow won't do that for you). Would close the Issue (or whatever the equivalent of "close" might be) if that is a supported option for the project management system.https://staging.gitlab.com/alexwilkinson/git-flower/-/issues/5Creates Pivotal Story Even Though There are Unstaged or Uncommited Changes2017-07-11T03:41:25Zusername-removed-889669Creates Pivotal Story Even Though There are Unstaged or Uncommited Changeshttps://staging.gitlab.com/alexwilkinson/git-flower/-/issues/4Prompt for Git Flow Install At Beginning of Scripts2017-07-10T16:23:28Zusername-removed-889669Prompt for Git Flow Install At Beginning of ScriptsRight now you can successfully get through most of the script, actually creating a ticket on a project management API, but then fail to create the branch locally because you do not have git-flow installed for that repository. Should prob...Right now you can successfully get through most of the script, actually creating a ticket on a project management API, but then fail to create the branch locally because you do not have git-flow installed for that repository. Should probably prompt to install it with instructions much earlier on, since it's such a huge dependency. Would rather that the script always succeed to create the local branch and fail the API call than the opposite.
Likely blocks #2 and #3 because they call for a similar error, and doing this work first will change how those two Issues are resolved.https://staging.gitlab.com/alexwilkinson/git-flower/-/issues/3Exception When There is No Develop Branch on Origin2017-07-10T16:22:59Zusername-removed-889669Exception When There is No Develop Branch on OriginThis will likely require a similar solution to #2.This will likely require a similar solution to #2.https://staging.gitlab.com/alexwilkinson/git-flower/-/issues/2Exception When There is No Develop Branch2017-07-10T16:18:19Zusername-removed-889669Exception When There is No Develop BranchShould probably have a more helpful error when a develop branch isn't present on the repository. Something about prompting to make sure you're git-flow ready, perhaps.Should probably have a more helpful error when a develop branch isn't present on the repository. Something about prompting to make sure you're git-flow ready, perhaps.username-removed-889669username-removed-889669