mitrandir77

4 ms·

1.
by mitrandir77 4y ago
Yup, it's automatic rebase of a commit on top of the newer (amended) version of its parent.
2.
by mitrandir77 4y ago
Nobody commented on the web interface yet which I think it's one of our coolest features: https://sapling-scm.com/docs/addons/isl
3.
by mitrandir77 4y ago
https://news.ycombinator.com/item?id=33615077
4.
by mitrandir77 4y ago
I don't see why merge conflicts would be a pain specific to monorepos. The merge conflict arises when you and some other person modify the same parts of the same file. No matter the repo size the correct solution here is figuring out t
5.
by mitrandir77 4y ago
You `sl commit` that half-done work anyway and then iterate by running `sl amend` many times until your commit is finished. In case you want to amend just part of changes us `sl amend -i` https://sapling-scm.com/docs/co
6.
by mitrandir77 4y ago
`sl histedit` is very similar to `git rebase -i` if you're famiilar with that interface which works just fine. Other commands useful for amending changes to previous commits: * `sl goto --merge <hash>` - if theres no conflicts yo
7.
by mitrandir77 4y ago
Phabricator was opensourced by Facebook. But most of it life as an opensource product is was actively maintained by Phacility.
8.
by mitrandir77 4y ago
It's simply not necessary to have that feature. Sapling encourages regularly committing and amending commits rather than staging changes. It's also easy to commit / amend part of your work by selecting the lines to include in
9.
by mitrandir77 4y ago
I've tried one very basic terminal rendering benchmark I had at hand [1] and on my MacBook Pro it was 17x faster than iterm and 3x faster than wezterm which is my daily driver. https://github.com/wez/wezterm/i
10.
by mitrandir77 4y ago
It is quite fast tbh and non-sluggish terminal is nice-to-have. I've tried one terminal rendering benchmark I had at hand [1] and on my MacBook Pro it was 17x faster than iterm and 3x faster than wezterm which is my daily driver. [1]