git-machete
git-machete copied to clipboard
VirtusLab
Probably the sharpest git repository organizer & rebase/merge workflow automation tool you've ever seen
Something like `ExistingLocalBranchShortName`, extending `LocalBranchShortName`, to be returned from `git_machete.client.MacheteClient.expect_in_managed_branches`? and expected in most places within `MacheteClient`
Forgive my skipping the issue template. I'm not sure if git machete is meant to be used for the common open-source workflow, where you're creating a PR from your fork...
A call to `read_definition_file` should return a fresh instance of `MacheteClient`.
Since some of the following steps in dry-run deploy depend on test PyPI, they always use the first-ever uploaded package for the given version :/ Proposed solution: use development versions...
After https://github.com/VirtusLab/git-machete/pull/891 and https://github.com/Homebrew/homebrew-core/pull/128562, man page is bundled into PyPI tarball and getting properly installed via Homebrew, hence preventing a crash at `git machete --help`. Still, this only works for...
Currently, both short and long hash are used: ``` Fork point for feature/foo is overridden to master (commit ce02c372e669). This applies as long as feature/foo is a descendant of commit...
The behavior of checking out the parent (i.e. a non-slid-out branch) makes sense when the current branch has been slid-out... but is confusing/surprising otherwise. Easiest to repro: ``` master foo...
Follow-up to #837 TBD if the case of diverged from & newer than remote should also be included (probably not)
Just as with `git_machete.client.MacheteClient.update`