git-machete
git-machete copied to clipboard
VirtusLab
Probably the sharpest git repository organizer & rebase/merge workflow automation tool you've ever seen
# Overview I'm fairly new to using Machete (please, don't throw tomatoes at me if I'm wrong in some of my Machete understanding :-)) I understood Machete as a tool...
Still need to decide whether it's allowed to add text to the current annotation or if it's not allowed to write at all but i would go with the latter...
- [ ] add a disclaimer in docs, with a link to https://github.com/VirtusLab/git-machete#can-i-use-git-merge-for-dealing-with-stacked-prs (I'd keep that link even in CLI docs) - [ ] maybe display a warning when `--merge`...
See https://github.com/VirtusLab/git-machete-intellij-plugin/issues/246#issuecomment-1281109198 and the following discussion. Maybe sth like `git machete traverse --create-github-prs`? TBD
What's the best way to break a tree of branches into smaller pieces? Either adding a new branch as a basis for an existing tree (the inverse of slide-out), or...
How open are you to receiving PRs for Gitlab integration? I want it so bad, I'm willing to do it :) If you are open to it, do you have...
To rename the current branch branch both in git and in .git/machete. See https://github.com/VirtusLab/git-machete-intellij-plugin/issues/1183 for further discussion. Optionally, `-b ` flag to act on non-current branch could be added to...
Only the branches that are really checked out should be affected.
# Based on PR #1249 ## Full chain of PRs as of 2024-05-08 * PR #1246: `fix/925-prs-from-forks` ➔ `fix/code-hosting-unexpected-errors` * PR #1249: `fix/code-hosting-unexpected-errors` ➔ `develop`
See #1240. For branches that were removed from remote, traverse should probably stop suggesting to push them, but instead suggest to slide them out (as with merged branches).