Be lazy and just commit
This provides the git lazy-commit command. This command can be used
in situations where you don't really care about choosing which
changes to track or writing your commit message -- you just want to
commit your work.
By its nature, git lazy-commit can very easily add accidental changes
to the git history if the user isn't careful. So, while this
tool may be appealing to git beginners, its target audience is
actually experienced git users who know when they want to break
the rules for creating good commits.
If you have staged changes (git add path/to/file), then
git lazy-commit will commit those staged changes. If you do not
have any staged changes, then git lazy-commit will commit all changes,
including untracked files (so be careful!).
git lazy-commit will write your commit message for you. If you've changed
a single file, the commit message will look like this:
Update www/index.html
If you've changed multiple files that share a similar directory, your commit message will look like this:
Update public/
- Update public/favicon.ico
- Create public/icons/favicon-16x16.png
- Create public/icons/favicon-32x32.png
If there aren't any similar directories that all changes share, or at least one of the updated files is in the root of the repository, your commit message will look like this:
Update files
- Update views.py
- Update templates/myapp/index.html
curl https://raw.githubusercontent.com/spenserblack/git-lazy-commit/main/install.sh | shYou may need to run this as an administrator.
Invoke-WebRequest "https://raw.githubusercontent.com/spenserblack/git-lazy-commit/main/install.ps1" | Invoke-ExpressionDownload the appropriate executable from the release assets,
rename it to git-lazy-commit, and add it to a location in PATH.
git lazy-commit can be annoying to type frequently, so you can create an alias
so that you only need to call git lzc.
git config --global alias.lzc lazy-commit