lucky-commit
extremely-linear
| lucky-commit | extremely-linear | |
|---|---|---|
| 10 | 9 | |
| 1,264 | 510 | |
| - | - | |
| 5.5 | 4.8 | |
| about 1 month ago | 2 months ago | |
| Rust | Shell | |
| MIT License | MIT License |
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.
lucky-commit
- Why you should pin your GitHub actions by commit-hash
- Lucky-commit: Customize your Git commit hashes
-
Linear Git History
See also Lucky Commit [0], which uses various types of whitespace characters instead of a hash inside the commit, which makes it look more magical.
I wonder about performance, though. Why is the author's method slower than the package I linked?
[0]: https://github.com/not-an-aardvark/lucky-commit
-
61a6666, is that rare?
It can also be reproduced. https://github.com/not-an-aardvark/lucky-commit
- Lucky-commit – Customize your Git commit hashes
- Lucky Commit – Customize your Git commit hashes
- Git-power: emPOWer your commits with bespoke hashes
-
Some joke about "Git is a blockchain" went too far, now we have this.
There is also lucky-commit, written in Rust, that has the same idea as git-power, but with GPU acceleration and the ability to choose a custom prefix. Looks like their Rust implementation (with or without GPU) is significantly faster than this C++ implementation. Crab language wins again, so it seems.
extremely-linear
- Extremely-Linear: Linear Git History
-
GitHub Sunsetting Subversion Support
It can be done, but probably shouldn't: https://github.com/zegl/extremely-linear/commits/main
- extremely-linear - Linear Git History
-
Linear Git History
I don't know if this is genius or stupid. But I've created a wrapper [1] for git (called "shit", for "short git") that converts non-padded revisions to their padded counterpart.
Examples:
"shit show 14" gets converted to "git show 00000140"
"shit log 10..14" -> "git log 00000100..00000140"
[1]: https://github.com/zegl/extremely-linear/blob/main/shit
- Extremely Linear Git History ^^
- Using CPU-only crashing... [creating a commit] takes ~43 seconds on the same computer
- Extremely Linear Git History
What are some alternatives?
delta - A syntax-highlighting pager for git, diff, and grep output
oxen-release - Lightning fast data version control system for structured and unstructured machine learning datasets. We aim to make versioning datasets as easy as versioning code.
git-absorb - git commit --fixup, but automatic
useless-git-tools
onefetch - Command-line Git information tool
Git - Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
bat - A cat(1) clone with wings.
gut - git helper scripts
git-power - git is a blockchain. Start your commit hashes with 00000000 like a real blockchain should.
teste
thefuck - Magnificent app which corrects your previous console command.