release-please
Our great sponsors
| release-please | semantic-pull-requests | |
|---|---|---|
| 46 | 1 | |
| 4,125 | - | |
| 7.6% | - | |
| 8.6 | - | |
| 7 days ago | - | |
| TypeScript | ||
| 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.
release-please
-
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.
-
Add a semver tag to release and auto increment it based on last tag
Check out https://github.com/googleapis/release-please
semantic-pull-requests
-
Keep a Changelog
* outside contributors get familiarized with the practice much faster (imagine getting new contributors to update changelogs)
We recently adopted this practice at Pyroscope and it's been working out pretty well for us [2], I can certainly recommend it.
[0] - https://github.com/apps/semantic-pull-requests
What are some alternatives?
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
conventional-chang
cz-cli - The commitizen command line utility. #BlackLivesMatter
chronicle - a fast changelog generator sourced from PRs and Issues
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
ESLint - Find and fix problems in your JavaScript code.
semantic-release - :package::rocket: Fully automated version management and package publishing
git-hook-conventional-commits-validator - A Git pre-commit hook which validates commit messages using Conventional Commits standard