gitjk
git-branchless
gitjk | git-branchless | |
---|---|---|
1 | 55 | |
826 | 3,308 | |
- | - | |
0.0 | 9.4 | |
almost 4 years ago | 8 days ago | |
JavaScript | Rust | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gitjk
-
A look how branches work in Git
I watched your demo video and I don't see any advantages over using named branches, and you describe no specific advantages in your README.
You just didn't give your branch a name, and referred to commits by ID. Fine, I guess, but are names so bad that you're gonna adopt a non-standard git workflow?
`git undo` is cool. There have been a number of fun variations on it over the years, and yours seems fine, but it's usually a leaky abstraction. I expect that yours is, too, but that's just because git itself is a leaky abstraction; it's just really hard to build a strong foundation on sand.
https://github.com/mapmeld/gitjk
git-branchless
-
Ask HN: Can we do better than Git for version control?
Yes, but due to its simplicity + extensibility + widespread adoption, I wouldn’t be surprised if we’re still using Git 100+ years from now.
The current trend (most popular and IMO likely to succeed) is to make tools (“layers”) which work on top of Git, like more intuitive UI/patterns (https://github.com/jesseduffield/lazygit, https://github.com/arxanas/git-branchless) and smart merge resolvers (https://github.com/Symbolk/IntelliMerge, https://docs.plasticscm.com/semanticmerge/how-to-configure/s...). Git it so flexible, even things that it handles terribly by default, it handles
- Meta developer tools: Working at scale
- Show HN: Gut – An easy-to-use CLI for Git
-
Branchless Workflow for Git
> Is this for a case where a bunch of people branch from master@HEAD (lets call this A), then you need to modify A, so you then need to rebase each branch that branched from A individually?
Mainly it's for when you branch from A multiple times, and then modify A. This can happen if you have some base work that you build multiple features on top of. I routinely do this as part of rapid prototyping, as described here: https://github.com/arxanas/git-branchless/wiki/Workflow:-div...
`git undo` shows a list of operations it'll execute, which you have to confirm before accepting. Of course, it's ultimately a matter of trust in the tools you use.
- Where are my Git UI features from the future?
- git-branchless: High-velocity, monorepo-scale workflow for Git
- git-branchless
-
Show HN: Maiao, Stacked Diffs for GitHub
What happens is you work somewhere that has stacked diffs and suddenly you learn how to shape your diffs to make them easy to review. Thinking of how folks will review your code in chunks while writing it makes it cleaner. Having small but easy to read diffs makes reviews faster and helps junior devs learn how to review.
Sometimes this doesn’t happen in which case you end up need to split your commit at the end. This is where git utterly fails. You end up needing git split and git absorb to make this productive.
Git split let’s you select which chunks in a commit should belong to it and then splits that into a commit and then you do it again and again until you have lots of commits. You’ll still need to probably test each one but the majority of the work is done
Git absorb takes changes on the top of your stack and magically finds which commit in your stack the each chunk should belong to and amends it to the right commit
You also need git branchless https://github.com/arxanas/git-branchless as it lets you move up and down the stack without needing to remember so much git arcana.
- High velocity, monorepo-scale workflow for Git
What are some alternatives?
git-extras - GIT utilities -- repo summary, repl, changelog population, author commit percentages and more
graphite-cli - Graphite's CLI makes creating and submitting stacked changes easy.
cz-cli - The commitizen command line utility. #BlackLivesMatter
jj - A Git-compatible VCS that is both simple and powerful
git-undo - Undo what you just did in git
magit - It's Magit! A Git Porcelain inside Emacs.
husky - Git hooks made easy 🐶 woof!
vimagit - Ease your git workflow within Vim
lazygit - simple terminal UI for git commands
libgit2 - A cross-platform, linkable library implementation of Git that you can use in your application.
legit - Git for Humans, Inspired by GitHub for Mac™.
git-stack - Stacked branch management for Git