traject
conventional-changelog
| traject | conventional-changelog | |
|---|---|---|
| 1 | 12 | |
| 99 | 7,612 | |
| - | 0.5% | |
| 4.2 | 9.1 | |
| 4 months ago | 8 days ago | |
| Ruby | TypeScript | |
| MIT License | ISC 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.
traject
-
Keep a Changelog
I don't think I understand what "squashing PR branches" means (a github feature I haven't noticed?), but:
> The real benefit here is that Github puts the PR URL into the squashed commit message.
While not in the commit message, github will show you the PR a commit is part of in it's commit view regardless. Which I do find invaluable for tracing the documentation of a change, agreed! Not everyone knows about this feature (I don't think it's been there forever) in github UI.
Eg notice the `#279` included in this github commit UI display (the PR was, I'm pretty sure, not "squashed").
https://github.com/traject/traject/commit/10339e774e92e57f44...
conventional-changelog
-
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 📦🚀
-
Using semantic-release to automate releases and changelogs
conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.
-
Conventional Commits - Specification for Your Commit Messages
Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog
-
Minor imperfections that shout ‘beginner code’
Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.
- GitHub Actions can't find built binaries to put them to a release
- FRONT END - LINKS CRIATIVOS E TÉCNICOS
-
Confused about how to get my packages up to `1.0.0` using Lerna / Conventional commits...
I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.
-
Automatically update git major tags on GitHub marketplace release
conventional-changelog-conventionalcommits
-
Keep a Changelog
[1] - https://github.com/conventional-changelog/conventional-chang...
-
What are some good practices for writing changelogs/update notes?
I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.
What are some alternatives?
conventional-chang
keep-a-changelog - If you build software, keep a changelog.
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
release-please - generate release PRs based on the conventionalcommits.org spec
Release It! 🚀 - 🚀 Automate versioning and package publishing
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
npm - :ship: semantic-release plugin to publish a npm package