Paweł Lipski
Paweł Lipski
Currently the generated easy-install launcher script looks like: ``` #!/usr/bin/python # EASY-INSTALL-SCRIPT: 'git-machete==3.0.0','git-machete' __requires__ = 'git-machete==3.0.0' __import__('pkg_resources').run_script('git-machete==3.0.0', 'git-machete') ``` Importing `pkg_resources` and its transitive deps takes around 300ms on my...
The logic is pretty complicated, mostly due to the presence of the underlying DFS that collects the chain of _next sibling for ancestor_ for each branch. This DFS can stay......
See the logs of e.g. https://app.circleci.com/pipelines/github/VirtusLab/git-machete/2171/workflows/54137532-fc50-445e-bed5-d9d84b936264/jobs/10118. By _no longer supported_ they seem to really mean _deprecated_, coz the pipeline still passed. Anyway, a migration would be a good idea 😅...
Like with `git_machete.client.MacheteClient.create_github_pr`. Mostly to prevent confusing order of params of the same type (such that mypy wouldn't capture if params are swapped). Generally, `create_github_pr` isn't in fact the best...
I mean... we could pass `--preserve-merges` to `git rebase` but I don't think that's really the best approach. In fact, out of 3 things: * true (aka 2-parent) merges *...
Should they even be? probably not... the only case where it would matter is for re-running a failed `master` build... but why would you even do it? probably hoping that...
It turned out particularly brittle compared to fish and zsh 😅 Regressions are very common every time something is added/changed... let's research if it can be reasonable tested at all.
Firstly, investigate docs creation literature, maybe there is some internationally approved nomenclature. They're easily confused with each other... mostly thanks to them being Latin, not English ~abbreviation~ ~acronym~ initialisms. _Automate...
Like in https://github.com/obsproject/obs-studio/issues/new/choose:  See https://github.com/obsproject/.github/tree/master/.github/ISSUE_TEMPLATE for the implementation
In particular, I'm not happy about `rebase` calling `machete-pre-rebase` hook, which is a git-machete-specific thing. TBD what else should me moved away from git_operations.py (Ctrl+F for `machete`).