committed
gnulib
| committed | gnulib | |
|---|---|---|
| 5 | 7 | |
| 94 | 264 | |
| - | 1.5% | |
| 7.9 | 9.8 | |
| 2 days ago | 4 days ago | |
| Rust | C | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
committed
-
Any good alternative to husky in rust to enforce and write conventional commits and for pre-commit source code linting??
I use https://github.com/crate-ci/committed and pre-commit (the python app)
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
committed just reads commit messages between a range of commits, after resolving refs
-
Ouch 0.3.0 released!
For colors, I've found yansi to be great to work with. I then use concolor-control (example) and `concolor-clap (no clap3 support yet, example part 1 and example part 2). As you can see, I also like to organize my colors by the styling role they fill. The only reason I wrapped in that example is its part of the crate's API and didn't want the public API tied to yansi.
-
Git-cliff: generate changelog files from the Git history
While auto-generated changelogs aren't the best, they are better than nothing. Too often I've seen projects without a changelog which is especially annoying when dealing with breaking changes.
I've been considering switching to a changelog generator, either from Conventional Commits or from a folder of files just to avoid merge conflicts with the CHANGELOG file.
If people want enforcement of Conventional Commit, check out https://github.com/crate-ci/committed
- Committed – A commit message linter optionally supporting conventional commits
gnulib
-
sha256sum written in Python faster than GNU version in C?
This appears to be the coreutil code.
-
Git-cliff: generate changelog files from the Git history
gnulib and a lot of GNU projects have this for a long time. https://github.com/coreutils/gnulib/blob/master/build-aux/gi...
- How do you confirm action on command line?
-
Do the coreutils rely on each other to work?
do_move calls a copy function from copy.c , which ends up in calling a renameatu function which ends up calling a SYS_renameat2 system call
-
why is dd so slow??
https://github.com/coreutils/gnulib/blob/master/lib/stat-size.h#L20-L21 ST_BLKSIZE(s): Preferred (in the sense of best performance) I/O blocksize for the file, in bytes.
-
https://np.reddit.com/r/linuxquestions/comments/mjepb0/why_is_dd_so_slow/gtalvhp/
https://github.com/coreutils/gnulib/blob/master/lib/stat-size.h#L20-L21
-
why are the executables, [ and test, a 4 kb difference?
So what do they do? Well, let's have a look:
What are some alternatives?
auto-changelog-action
coreutils - upstream mirror
onefetch - Command-line Git information tool
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
github-changel
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
shipkit-changelog - Minimalistic Gradle plugin that generates changelog based on commit history and GitHub pull requests/issues
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
freebsd-src - The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests....