git-snap
Create snapshot commits on a not checked-out branch without touching the working tree or losing staged changes (by meribold)
release-please
generate release PRs based on the conventionalcommits.org spec (by googleapis)
| git-snap | release-please | |
|---|---|---|
| 4 | 47 | |
| 11 | 4,199 | |
| - | 4.3% | |
| 0.0 | 8.5 | |
| over 1 year ago | 16 days ago | |
| Shell | TypeScript | |
| - | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
git-snap
Posts with mentions or reviews of git-snap.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-18.
- Show HN: Git command for creating snapshot commits on a not checked-out branch
- Script for creating snapshot commits on a not checked-out branch without touching the working tree
-
Use Git Tactically
I have a `git snap` command that does this. It creates a commit on a machine-specific snapshots branch with a fixed commit message. It doesn't touch the working directory and restores everything else (HEAD and the index) after making the commit.
https://github.com/meribold/git-snap
release-please
Posts with mentions or reviews of release-please.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-05-04.
-
Git commit helper: add emojis to your commits
Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀
-
How to write GIT commit messages
Conventional Commits
-
How to Improve Development Experience of your React Project
We've covered everything about writing well-formatted and structured code without worrying too much about it anymore. The only part we haven't explored yet is linting commit messages. Commitlint will help us here. It allows you to configure any rules you want for the commit message, but we're going to use the Conventional Commits specification, one of the most popular conventions you'll find.
- Release Please
-
TypeScript Boilerplate
Commit Management with Conventional Commits: The Conventional Commits methodology is adopted to maintain a clear and structured record of changes with the help of commitlint.
-
A Gitlab Review Bot Assistant
Validate if the commit titles adhere to the Conventional Commits Specification in Merge requests.
-
Ask HN: Should commit summaries describe the change, or the intent?
Check out https://www.conventionalcommits.org
-
Announcing release-plz v0.3.0
FYI there is already a popular tool that does just this with a very similar name: https://github.com/googleapis/release-please
-
A clean Git history with Git Rebase and Conventional Commits
The feature commit should have a clear defined message - Don't re-invent here - There exists a fairly used and accepted convention called Conventional Commits, so we are going to use that.