Paweł Lipski
Paweł Lipski
https://git-machete.readthedocs.io/en/stable/#diff says: > Runs git diff of the given branch tip against its fork point or, if none specified, of the current working tree against the fork point of the...
Only if: * it exists (under the name `v`, see the existing closed milestones * it is empty (no issues or PRs left)
A sample failure (I tried to run the test newly-added on #594 against code without `client.py` changed): ``` ================================================================================================================== FAILURES ================================================================================================================== _______________________________________________________________________________ TestStatus.test_status_when_child_branch_is_pushed_immediately_after_creation ________________________________________________________________________________ [gw0] linux -- Python 3.10.5 /home/plipski/git-machete/.tox/py310/bin/python...
Too much text appears, I tried to show the gif as a demo to my folks and couldn't keep up with what happens 😅
So that it's no longer needed to add a tap.
It's been neglected, mostly coz I relied on GitHub automatically retargeting the child PRs once parent PR is merged... but I've recently realized that this behavior only applies when the...
As for now, the subcommands like `create-pr` can't be linked directly... just the entire `github` command can be linked to by https://git-machete.readthedocs.io/en/stable/#github. Consider the same for other commands/help topics, like...
That's a recurring minor nuisance with no serious consequences really... but would be nice to fix anyway, once and for good preferably (in all places, not just here). I'd expect...
https://anaconda.org/conda-forge/git-machete Does it install correctly on Mac/Linux? Maybe worth: * mentioning in README.md as a way to install * adding a badge to README.md
`upstream` is somewhat brittle as it is used by git itself to signify remote tracking branch, see e.g. `git show @{upstream}` TBD what to do... preferably stick to parent/child naming...