semantic-release
commitlint
Our great sponsors
semantic-release | commitlint | |
---|---|---|
75 | 27 | |
19,768 | 15,959 | |
1.6% | 1.8% | |
9.4 | 9.6 | |
5 days ago | 5 days ago | |
JavaScript | TypeScript | |
MIT License | MIT 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.
semantic-release
- alacritty-themes not working any more!!!
- Announcing @ngneat/avvvatars
- Auto versioning?
-
Is it possible to bypass merge queue requirement for a GitHub app without needing admin permissions?
I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.
-
How to set up Commitzen with Husky
Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.
-
Automated release with Semantic Release and commitizen
When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.
- π¦ Effortless Data Quality w/duckdb on GitHub βΎοΈ
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.
- Automated Release Notes in Azure Devops
-
What are some examples of good release notes from open source projects that you have come across?
If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release
commitlint
-
How to use Lefthooks in your node project?
Apart from these we also need to enforce standards for all our commit messages(commit-lint).
-
Better Git Commits with `@commitlint`
There are many features of commitlint that I can't mention one by one, as well as installation guide. To know the detail you can directly access https://github.com/conventional-changelog/commitlint.
-
Conventional Commit Message and Linting
These commit message prefixes can help to provide context and organization in a project's version control history, making it easier to understand and track changes over time. Note: if you want to force these rules on commit messages, here is a commit linting lib for you. Commitlint
-
Nodejs Boilerplate with Typescript and Express
Commit Lint
-
Setting Up a Modern Preact Application With Typescript, Vite and Vitest
I personally find it quite useful to enforce a uniform commit style. commitlint pairs well with husky.
-
How to enforce Conventional Commit messages using Git hooks with husky & commitlint
β§ input: Set up Conventional Commits using Husky and commitlint β subject may not be empty [subject-empty] β type may not be empty [type-empty] β found 2 problems, 0 warnings β Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint husky - commit-msg hook exited with code 1 (error)
-
Commit message linting within Magit?
Can setup tools like Commitlint to add hooks that will reject a commit message if it is invalid, but if you format a commit message incorrectly it simply closes the commit buffer and returns to git status, meaning you have to retype out your commit message, which is obviously less than ideal.
-
π Angular 14 + ESLint, Material + Transloco + Jest, TestCafe + Docker + Prettier π
β Angular 14 β Angular Material β Unit Testing with Jest β End-to-End Testing with TestCafΓ© β Internationalization with Transloco β Auto documentation with Compodoc β Analyse your project with source-map-explorer β Docker β ESLint β Prettier β Commit Linting
- Require commit-msg hook for all users...
-
commitlint VS lintje - a user suggested alternative
2 projects | 11 Sep 2022
What are some alternatives?
GitVersion - From git log to SemVer in no time
lint-staged - π«π© β Run linters on git staged files
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
husky - Git hooks made easy πΆ woof!
Release It! π - π Automate versioning and package publishing
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
release-drafter - Drafts your next release notes as pull requests are merged into master.
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles
emoji-commit-messages - π΅ A fun paradigm to encourage cleaner commits.
semver - Semantic Versioning Specification
create-nuxt-app - Create Nuxt.js App in seconds.