xsteadfastx/conventionalcommits.org
1
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2024-11-14 10:35:14 +01:00
Code Issues Projects Releases Wiki Activity

ui: move about to another page (#381)

Browse Source
This commit is contained in:
Damiano Petrungaro 2021-07-12 22:43:00 +02:00 committed by GitHub
parent 6b8e9b1bf5
commit 1f87df8018
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
54 changed files with 138 additions and 1979 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
archetypes/about.md Normal file
View File

@ -0,0 +1,4 @@
---
type: about
draft: true
---

82
content/about/index.md Normal file
View File

@ -0,0 +1,82 @@
---
type: about
draft: false
---
# About
The Conventional Commits specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
The first draft of this specification has been written in collaboration with some of the folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a set of tools for parsing Conventional Commits messages from git histories.
* [parse-commit-message](https://npmjs.com/package/parse-commit-message): Extensible utilities for parsing, stringify and validating Conventional Commit messages.
* [bumped](https://bumped.github.io): a tool for releasing software that makes it easy to perform actions before and after releasing a new version of your software.
* [unleash](https://github.com/netflix/unleash): a tool for automating the software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out of the Babel project.
## Tooling for Conventional Commits
* [go-conventionalcommits](https://github.com/leodido/go-conventionalcommits): Full Go powers to parse conventional commits
* [go-conventional-commit](https://gitlab.com/digitalxero/go-conventional-commit14): go library for parsing commit messages following the specification.
* [chglog](https://github.com/goreleaser/chglog): a tool for parsing Conventional Commits messages from git histories and turning them into templateable change logs.
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): follows the specification to manage versions and generate a changelog automatically
* [commitizen/cz-cli](https://github.com/commitizen/cz-cli): A Node.js tool to create commit messages following the Conventional Commits specs.
* [commitizen-tools/commitizen](https://github.com/commitizen-tools/commitizen): A tool written in Python to create commiting rules for projects, auto bump versions and auto changelog generation.
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): A PHP tool built to create commit messages following the Conventional Commits specs.
Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [php-conventional-changelog](https://github.com/marcocesarato/php-conventional-changelog): a tool built to generate a changelog from a project's committing history messages and metadata and automate versioning with Semver, following Conventional Commits specs. Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [commitlint](https://github.com/conventional-changelog/commitlint): A linter to check that your commit messages meet the Conventional Commits format.
* [gitlint](https://github.com/jorisroovers/gitlint): Git commit message linter written in Python, which can be configured to [enforce Conventional Commits format](https://jorisroovers.com/gitlint/contrib_rules/#ct1-contrib-title-conventional-commits).
* [conform](https://github.com/autonomy/conform): a tool that can be used to enforce policies on git repositories, including Conventional Commits.
* [detect-next-version](https://npmjs.com/package/detect-next-version): Parse, detect and get more metadata about given Conventional Commits.
* [recommended-bump](https://www.npmjs.com/package/recommended-bump): Calculcates the recommended version bump based on given Conventional Commits.
* [git-commits-since](https://www.npmjs.com/package/git-commits-since): Get all (raw) commits since period or (by default) from latest git SemVer tag, plus plugins support.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): provides extensible context and template-based completion, and inspections, for Conventional Commits inside the VCS Commit dialog. Available for all [JetBrains IDEs](https://www.jetbrains.com/).
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Add Conventional Commits support to [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are Conventional Commits compliant. Comes with Docker image for CI uses.
* [semantic-release](https://github.com/semantic-release/semantic-release): A tool that automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package.
* [python-semantic-release](https://github.com/relekang/python-semantic-release): Automatic Semantic Versioning for Python projects. This is a Python implementation of the [semantic-release](https://github.com/semantic-release/semantic-release) for Node.js.
* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): Add Conventional Commits supports for VSCode.
* [Pyhist](https://github.com/jgoodman8/pyhist): A Python utility to automagically update the package version from the git history and generate the Changelog.
* [git-mkver](https://github.com/idc101/git-mkver): A tool to automatically apply Semantic Versioning to git repositories based on _Conventional Commits_.
* [Conventional Commits Next Version](https://gitlab.com/DeveloperC/conventional_commits_next_version): A tooling and language agnostic utility to calculate the next semantic version based on the _Conventional Commits_ since the prior version. Supports monorepos.
* [change](https://github.com/adamtabrams/change): A tool for generating and updating a changelog using Conventional Commits.
* [Turbogit](https://b4nst.github.io/turbogit): A command line tool to help you follow _Conventional Commits_ flow.
* [sv4git](https://github.com/bvieira/sv4git): A command line tool (CLI) to validate commit messages, bump versions, create tags and generate changelogs.
* [Versio](https://github.com/chaaz/versio): A monorepo-compatible tool that updates version numbers based on conventional commits and project dependencies. It can generate tags and changelogs, too.
* [Git Changelog Lib](https://github.com/tomasbjerre/git-changelog-lib): A Java library that supports rendering a changelog given a context derived from Git. Supports conventional commits with [Handlebars Helpers](https://github.com/tomasbjerre/git-changelog-lib#helpers). It is used in:
* [Gradle](https://github.com/tomasbjerre/git-changelog-gradle-plugin)
* [Maven](https://github.com/tomasbjerre/git-changelog-maven-plugin)
* [Jenkins](https://github.com/jenkinsci/git-changelog-plugin)
* [Command Line](https://github.com/tomasbjerre/git-changelog-command-line)
## Projects Using Conventional Commits
* [NFPM](https://github.com/goreleaser/nfpm): NFPM is Not FPM - a simple deb, rpm and apk packager written in Go
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools and libraries for adding test coverage to your JavaScript tests.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) and [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optional supplemental user interface enhancing [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): A data access library for Node and PostgreSQL.
* [electron](https://github.com/electron/electron): Build cross-platform desktop apps with JavaScript, HTML, and CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): A simple to use scroll utility package for centering elements, and smooth animations
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free open source UI toolkit.
* [Monica](https://github.com/monicahq/monica): An open source personal relationship management system.
* [mhy](https://mhy.js.org): A zero-config, out-of-the-box, multi-purpose toolbox and development environment.
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): Simple parser for Diff files (unified diff format).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): Easy split of .diff & .patch into its files.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo of ~100 TypeScript projects for data driven development
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 An enhanced Yii2 app template.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Template to easily and quickly create your online CV.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
* [Tina CMS](https://tinacms.org): An open source toolkit for building front-end content-management into your website.
* [Belajarpython](https://github.com/belajarpythoncom/belajarpython.com) Open source Indonesian python programming tutorial site.
* [Uno Platform](https://platform.uno): Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
* [Jenkins X](https://jenkins-x.io/): Jenkins X provides pipeline automation, built-in GitOps, and preview environments to help teams collaborate and accelerate their software delivery at any scale.
* [Changeloguru](https://github.com/haunt98/changeloguru): Auto-generate changelog from conventional commits, written in Go.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

20
content/v1.0.0-beta.1/index.it.md
View File

@ -138,23 +138,3 @@ Semplicemente il commit verrà ignorato dai tool che sono basati su questa speci
No. Se usi un workflow basato sugli squash di Git, i mantenitori possono pulire i messaggi dei commit mentre vengono inseriti nel branch principale (merge), non aggiungendo alcun carico di lavoro ai committer occasionali.
Un workflow comune è quello di unire (con lo squash) automaticamente i commit dalle pull request e far utilizzare un form ai mantenitori per riscrivere un messaggio più adeguato.
## Riguardo
La specifica Commit Convenzionali è ispirata e fortemente basata su [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
La prima bozza di questa specifica è stata scritta in collaborazione con alcuni contributori di:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un set di tool per analizzare messagi dei commit convenzionali dalla cronologia git.
* [unleash](https://github.com/netflix/unleash): un tool per automatizzare rilasci e cicli di pubblicazioni di un software.
* [lerna](https://github.com/lerna/lerna): un tool per la gestione di monorepos, nato del progetto Babel.
## Progetti che usano Commit Convenzionali
* [yargs](https://github.com/yargs/yargs): Parser di argomenti da CLI, a tema pirati.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): Una collezione di strumenti e librerie open source per aggiungere la coverage dei test JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatizza il versionamento e la gestione del CHANGELOG utilizzando il nuovo pulsante squash di GitHub e il flusso di lavoro consigliato da Commit Convenzionali.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_vuoi aggingere il tuo progetto alla lista?_ [invia una pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

26
content/v1.0.0-beta.1/index.md
View File

@ -131,29 +131,3 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About
The Conventional Commit specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
The first draft of this specification has been written in collaboration with some of the
folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a
set of tools for parsing conventional commit messages from git histories.
* [unleash](https://github.com/netflix/unleash): a tool for automating the
software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out
of the Babel project.
## Projects Using Conventional Commits
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools
and libraries for adding test coverage to your JavaScript tests.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

21
content/v1.0.0-beta.1/index.pl.md
View File

@ -132,24 +132,3 @@ Po prostu znaczy to, że będzie pominięty przez narzędzia bazujące na specyf
Nie! Jeśli używasz trybu bazującego na spłaszczaniu historii dostarczeń, wtedy główni opiekunowie projektu mogą posprzątać wiadomości
podczas dostarczania. Takie podejście nie narzuca żadnego obowiązku na osoby dostarczające od czasu do czasu. Powszechnym podejściem
jest używanie automatycznego spłaszczania historii dostarczeń z prośby wciągnięcia (pull request) oraz wyświetlenie formularza osobie dostarczającej w celu wypełnienia wiadomości poprawną treścią.
## O twórcy
Specyfikacja Konwencjonalnych Commitów jest inspirowana oraz mocno bazuje na [Wytycznych Commitów Angulara](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
Pierwsza wersja tej specyfikacji została stworzona we współpracy z kilkoma kontrybutorami takich projektów jak:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): zbiór narzędzi
pozwalających na parsowanie konwencjonalnych commitów z historii `git`owych dostarczeń.
* [unleash](https://github.com/netflix/unleash): narzędzie do automatyzacji wydawania oraz publikowania.
* [lerna](https://github.com/lerna/lerna): narzędzie do zarządzania mono-repozytoriami, które wyrosło z projektu Babel.
## Projekty używające Konwencjonalnych Commitów
* [yargs](https://github.com/yargs/yargs): uwielbiany przez wszystkich, piracko stylizowany parser argumentów linii komend.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): kolekcja otwarto-źródłowych narzędzi oraz bibliotek do dodawania miar pokrycia kodu do Twoich testów jednostkowych
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatyczne zarządzanie wersjami oraz DZIENNIKIEM ZMIAN, używający nowego przycisku Spłaszcz na GitHubie oraz trybu pracy opartego o Konwencjonalne Commity.
[![Konwencjonalne Commity](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_chcesz, aby Twój projekt znajdował się na tej liście?_ [stwórz pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

22
content/v1.0.0-beta.1/index.zh-hans.md
View File

@ -104,25 +104,3 @@ draft: false
### 所有的贡献者都需要使用约定式提交规范吗？
并不！如果你使用基于 squash 的 Git 工作流，主管维护者可以在合并时清理提交信息——这不会对普通提交者产生额外的负担。有种常见的工作流是让 git 系统自动从 pull request 中 squash 出提交，向主管维护者提供表单，来在合并时输入合适的 git 提交信息。
## 关于
约定式提交规范受到了 [Angular 提交准则](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)的启发，并在很大程度上以其为依据。
该规范的首个草案来自下面这些项目中若干贡献者们的协作：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)：一套从 git 历史中解析出约定式提交说明的工具。
* [unleash](https://github.com/netflix/unleash)：一个用于自动化软件发行和发布生命周期的工具。
* [lerna](https://github.com/lerna/lerna)：一个用于管理宏仓库的工具，源自 Babel 项目。
## 使用约定式提交的项目
* [yargs](https://github.com/yargs/yargs)：广受欢迎的命令行参数解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)：一套为 JavaScript 测试生成测试覆盖率的开源工具和类库。
* [standard-version](https://github.com/conventional-changelog/standard-version) 基于 GitHub 的新 squash 按钮与推荐的约定式提交工作流，自动管理版本和 CHANGELOG。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 和 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)：用于增强 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可选用户界面。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想让你的项目出现在上面吗？_[提交 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

29
content/v1.0.0-beta.2/index.es.md
View File

@ -214,32 +214,3 @@ adicionales a quienes contribuyen casualmente. Un flujo de trabajo común para
esto es configurar su sistema de git para que haga el `squash` de manera
automática de un pull request y presente al líder del proyecto un formulario
para que ingrese el mensaje de commit correcto al momento de hacer el merge.
## Acerca de
La especificación de Commits Convencionales está inspirada, y fuertemente
basada, en [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
El primer borrador de esta especificación ha sido escrito en colaboración con
algunos de los colaboradores de:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog):
una serie de herramientas para analizar los mensajes de los commits de los
historiales de git.
* [unleash](https://github.com/netflix/unleash): una herramienta para
automatizar la liberación de software y ciclo de vida de publicación.
* [lerna](https://github.com/lerna/lerna): una herramienta para manejar
mono-repositorios, que creció a partir del proyecto Babel.
## Proyectos usando Commits Convencionales
* [yargs](https://github.com/yargs/yargs): el analizador de argumentos de la línea de comandos preferido por todos.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): una colección de herramientas y librerías de código abierto para agregar cobertura de código a sus tests.
* [standard-version](https://github.com/conventional-changelog/standard-version): versionado automático y manejos de CHANGELOG, usando el botón de squash de GitHub y siguiendo el flujo de trabajo de los Commits Convencionales.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) y [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): mejoramiento opcional para la interfaz de usuario [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): Simple parser para archivos Diff (formato unified diff).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): Herramienta fácil para separar .diff y .patch en sus archivos de diferencias contenidos.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_¿Quiere ver su proyecto en esta lista?_ [haga un pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

28
content/v1.0.0-beta.2/index.fr.md
View File

@ -158,31 +158,3 @@ Dans le pire des cas, ce n'est pas la fin du monde si un commit atterrit sans re
### Est-ce que tous mes contributeurs doivent utiliser les spécifications de Conventional Commits ?
Non! Si vous utilisez un flux de travail basé sur squash sur Git, les responsables principaux peuvent nettoyer les messages des commits au fur et à mesure de leur fusion, ce qui permet de ne pas ajouter de charge de travail aux committers occasionnels. Un processus courant consiste à ce que votre système git écrase automatiquement les commits d'une demande d'extraction et présente un formulaire permettant au responsable de la maintenance d'entrer le message du commit git approprié pour la fusion.
## À Propos
La spécifications de Conventional Commits s’inspire largement de [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
La première version de ces spécifications a été rédigée en collaboration avec certains des
les gens qui contribuent à:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un
ensemble d'outils permettant d'analyser les messages des commits classiques à partir des historiques git.
* [unleash](https://github.com/netflix/unleash): un outil pour automatiser le
versioning d'un logiciel et du cycle de publication.
* [lerna](https://github.com/lerna/lerna): un outil de gestion de monorepos, qui a grandi
du projet Babel.
## Projets Utilisant Conventional Commits
* [yargs](https://github.com/yargs/yargs): Le parseur d'arguments en ligne de commande sur le thème des pirates préféré de tous.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Utilitaire d'analyse conforme aux spécifications pour obtenir un objet comme `{ header: { type, scope, subject }, body, footer }` à partir de la chaîne de message du commit.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): une collection d'outils open-source
et bibliothèques pour ajouter une couverture de test à vos tests JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Le versioning automatique et la gestion de CHANGELOG, en utilisant le nouveau bouton squash de GitHub et le flux de travail Conventional Commits recommandé.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) et [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Amélioration optionnelle de l'interface utilisateur [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [Formulaires Nintex](https://www.nintex.fr/plateforme-de-processus/#forms): Créez facilement des formulaires en ligne dynamiques pour capturer et soumettre des données précises et actuelles.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_envie d'avoir votre projet sur cette liste?_ [envoyer une pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

20
content/v1.0.0-beta.2/index.it.md
View File

@ -152,23 +152,3 @@ Non è la fine del mondo se un commit non segue la specifica Commit Convenzional
### Devono tutti i contributori seguire la specifica Commit Convenzionali?
No. Se usi un workflow basato sugli squash di Git, i mantenitori possono pulire i messaggi dei commit mentre vengono inseriti nel branch principale (merge), non aggiungendo alcun carico di lavoro ai committer occasionali. Un workflow comune è quello di unire (con lo squash) automaticamente i commit dalle pull request e far utilizzare un form ai mantenitori per riscrivere un messaggio più adeguato.
## Riguardo
La specifica Commit Convenzionali è ispirata e fortemente basata su [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
La prima bozza di questa specifica è stata scritta in collaborazione con alcuni contributori di:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un set di tool per analizzare messagi dei commit convenzionali dalla cronologia git.
* [unleash](https://github.com/netflix/unleash): un tool per automatizzare rilasci e cicli di pubblicazioni di un software.
* [lerna](https://github.com/lerna/lerna): un tool per la gestione di monorepos, nato del progetto Babel.
## Progetti che usano Commit Convenzionali
* [yargs](https://github.com/yargs/yargs): Parser di argomenti da CLI, a tema pirati.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): Una collezione di strumenti e librerie open source per aggiungere la coverage dei test JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatizza il versionamento e la gestione del CHANGELOG utilizzando il nuovo pulsante squash di GitHub e il flusso di lavoro consigliato da Commit Convenzionali.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_vuoi aggingere il tuo progetto alla lista?_ [invia una pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

28
content/v1.0.0-beta.2/index.md
View File

@ -156,31 +156,3 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About
The Conventional Commit specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
The first draft of this specification has been written in collaboration with some of the
folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a
set of tools for parsing conventional commit messages from git histories.
* [unleash](https://github.com/netflix/unleash): a tool for automating the
software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out
of the Babel project.
## Projects Using Conventional Commits
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Spec compliant parsing utility to get object like `{ header: { type, scope, subject }, body, footer }` from given commit message string.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools
and libraries for adding test coverage to your JavaScript tests.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) and [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optional supplemental user interface enhancing [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

22
content/v1.0.0-beta.2/index.pl.md
View File

@ -159,25 +159,3 @@ Po prostu znaczy to, że będzie pominięty przez narzędzia bazujące na specyf
Nie! Jeśli używasz trybu bazującego na spłaszczaniu historii dostarczeń, wtedy główni opiekunowie projektu mogą posprzątać wiadomości
podczas dostarczania. Takie podejście nie narzuca żadnego obowiązku na osoby dostarczające od czasu do czasu. Powszechnym podejściem
jest używanie automatycznego spłaszczania historii dostarczeń z prośby wciągnięcia (pull request) oraz wyświetlenie formularza osobie dostarczającej w celu wypełnienia wiadomości poprawną treścią.
## O twórcy
Specyfikacja Konwencjonalnych Commitów jest inspirowana oraz mocno bazuje na [Wytycznych Commitów Angulara](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
Pierwsza wersja tej specyfikacji została stworzona we współpracy z kilkoma kontrybutorami takich projektów jak:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): zbiór narzędzi
pozwalających na parsowanie konwencjonalnych commitów z historii `git`owych dostarczeń.
* [unleash](https://github.com/netflix/unleash): narzędzie do automatyzacji wydawania oraz publikowania.
* [lerna](https://github.com/lerna/lerna): narzędzie do zarządzania mono-repozytoriami, które wyrosło z projektu Babel.
## Projekty używające Konwencjonalnych Commitów
* [yargs](https://github.com/yargs/yargs): uwielbiany przez wszystkich, piracko stylizowany parser argumentów linii komend.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): kolekcja otwarto-źródłowych narzędzi oraz bibliotek do dodawania miar pokrycia kodu do Twoich testów jednostkowych
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatyczne zarządzanie wersjami oraz DZIENNIKIEM ZMIAN, używający nowego przycisku Spłaszcz na GitHubie oraz trybu pracy opartego o Konwencjonalne Commity.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) oraz [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Opcjonalny, uupełniający interfejs użytkownika ulepszający [Apereo uPortal](https://www.apereo.org/projects/uportal).
[![Konwencjonalne Commity](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_chcesz, aby Twój projekt znajdował się na tej liście?_ [stwórz pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

32
content/v1.0.0-beta.2/index.ru.md
View File

@ -176,35 +176,3 @@ fixes issue #12
историю всех предыдущих коммитов при их слияния, не добавляя рабочей нагрузки на случайные коммиты. Обычно,
рабочий процесс строится на том, что ваша система Git автоматически объединяет (squash) все предыдущие коммиты пред
перед pull-запросом и предоставляет форму сопровождающему проекта для ввода нового коммита.
## О спецификации
Общепринятые Коммиты вдохновлены и основаны на
[Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
Первый черновик спецификации был написан в сотрудничестве с некоторыми участниками:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): набор утилит для парсинга
стандартных сообщений коммитов из истории git.
* [bumped](https://bumped.github.io): утилита для релиза приложений, которая позволяет легко выполнять действия
до и после релиза новой версии ваших приложений.
* [unleash](https://github.com/netflix/unleash): утилита для автоматического релиза и публикации приложений.
* [lerna](https://github.com/lerna/lerna): утилита для управления моно-репозиториями, которая выросла и проекта Babel.
## Проекты, использующие Общепринятые Коммиты
* [yargs](https://github.com/yargs/yargs): всеми любимый парсер параметров командной строки.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): коллекция утилит и библиотек с открытым исходным кодом для оценки покрытия
тестами вашего кода.
* [standard-version](https://github.com/conventional-changelog/standard-version): автоматический менеджер версий
и CHANGELOG'ов, использующий GitHub `new squash` кнопку, который рекомендует использовать Общепринятые Коммиты.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) и [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame):
новый дополнительный пользовательский интерфейс [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): библиотека для доступа к данным PostrgeSQL для Node.
* [electron](https://github.com/electron/electron): утилита для создания крос-платформенных приложений на JavaScript, HTM и CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): простая в использовании утилита контроля прокрутки центральных
элементов и плавной анимации.
[![Общепринятые Коммиты](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_Хотите, чтоб ваш проект появился в этом списке?_ [Отправьте Pull Request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

23
content/v1.0.0-beta.2/index.zh-hans.md
View File

@ -133,26 +133,3 @@ fixes issue #12
### 所有的贡献者都需要使用约定式提交规范吗？
并不！如果你使用基于 squash 的 Git 工作流，主管维护者可以在合并时清理提交信息——这不会对普通提交者产生额外的负担。有种常见的工作流是让 git 系统自动从 pull request 中 squash 出提交，并向主管维护者提供一份表单，用以在合并时输入合适的 git 提交信息。
## 关于
约定式提交规范受到了 [Angular 提交准则](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)的启发，并在很大程度上以其为依据。
该规范的首个草案来自下面这些项目中若干贡献者们的协作：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)：一套从 git 历史中解析出约定式提交说明的工具。
* [unleash](https://github.com/netflix/unleash)：一个用于自动化软件发行和发布生命周期的工具。
* [lerna](https://github.com/lerna/lerna)：一个用于管理宏仓库（monorepo）的工具，源自 Babel 项目。
## 使用约定式提交的项目
* [yargs](https://github.com/yargs/yargs)：广受欢迎的命令行参数解析器。
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): 一个符合规范的解析工具，从给定的某个提交信息字符串中解析出形如 `{ header: { type, scope, subject }, body, footer }` 的对象。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)：一套为 JavaScript 测试生成测试覆盖率的开源工具和类库。
* [standard-version](https://github.com/conventional-changelog/standard-version) 基于 GitHub 的新 squash 按钮与推荐的约定式提交工作流，自动管理版本和 CHANGELOG。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 和 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)：用于增强 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可选用户界面。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想让你的项目出现在上面吗？_ [提交 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

41
content/v1.0.0-beta.3/index.es.md
View File

@ -196,44 +196,3 @@ adicionales a quienes contribuyen casualmente. Un flujo de trabajo común para
esto es configurar su sistema de git para que haga el `squash` de manera
automática de un pull request y presente al líder del proyecto un formulario
para que ingrese el mensaje de commit correcto al momento de hacer el merge.
## Acerca de
La especificación de Commits Convencionales está inspirada, y fuertemente
basada, en [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
El primer borrador de esta especificación ha sido escrito en colaboración con
algunos de los colaboradores de:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog):
una serie de herramientas para analizar los mensajes de los commits de los
historiales de git.
* [bumped](https://bumped.github.io): una herramienta para liberar software que facilita realizar acciones antes y después de lanzar una nueva versión de su software.
* [unleash](https://github.com/netflix/unleash): una herramienta para
automatizar la liberación de software y ciclo de vida de publicación.
* [lerna](https://github.com/lerna/lerna): una herramienta para manejar
mono-repositorios, que creció a partir del proyecto Babel.
## Herramientas para Commit Convencionales
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): una desarrollada para crear mensajes de confirmación según las especificaciones de Commits Convencionales.
Configurable y usable en proyectos de PHP como una dependencia de composer o utilizable globalmente para proyectos no PHP.
* [conform](https://github.com/autonomy/conform): una herramienta que se puede utilizar para aplicar políticas en los repositorios de git, incluidos los Commits Convencionales.
## Proyectos usando Commits Convencionales
* [yargs](https://github.com/yargs/yargs): el analizador de argumentos de la línea de comandos preferido por todos.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): una colección de herramientas y librerías de código abierto para agregar cobertura de código a sus tests.
* [standard-version](https://github.com/conventional-changelog/standard-version): versionado automático y manejos de CHANGELOG, usando el botón de squash de GitHub y siguiendo el flujo de trabajo de los Commits Convencionales.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) y [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): mejoramiento opcional para la interfaz de usuario [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://gitlab.com/dmfay/massive-js): una librería para el acceso a datos para Node y PostgreSQL
* [electron](https://github.com/electron/electron): Construya aplicaciones multi-plataforma con JavaScript, HTML y CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un paquete de utilidades de desplazamiento fácil de usar para centrar elementos y realizar animaciones
* [Blaze UI](https://github.com/BlazeUI/blaze): Kit de herramientas modular de código abierto sin frameworks.
* [Monica](https://github.com/monicahq/monica): Un sistema de gestión de relaciones personales de código abierto.
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): Simple parser para archivos Diff (formato unified diff).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): Herramienta fácil para separar .diff y .patch en sus archivos de diferencias contenidos.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_¿Quiere ver su proyecto en esta lista?_ [haga un pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

35
content/v1.0.0-beta.3/index.fr.md
View File

@ -143,38 +143,3 @@ Dans le pire des cas, ce n'est pas la fin du monde si un commit atterrit sans re
### Est-ce que tous mes contributeurs doivent utiliser les spécifications de Conventional Commits ?
Non! Si vous utilisez un flux de travail basé sur squash sur Git, les responsables principaux peuvent nettoyer les messages des commits au fur et à mesure de leur fusion, ce qui permet de ne pas ajouter de charge de travail aux committers occasionnels. Un processus courant consiste à ce que votre système git écrase automatiquement les commits d'une demande d'extraction et présente un formulaire permettant au responsable de la maintenance d'entrer le message du commit git approprié pour la fusion.
## À Propos
La spécifications de Conventional Commits s’inspire largement de [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
La première version de ces spécifications a été rédigée en collaboration avec certains des les gens qui contribuent à:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): Un ensemble d'outils permettant d'analyser les messages des commits classiques à partir des historiques git.
* [bumped](https://bumped.github.io): Un outil de publication de logiciel qui facilite l'exécution d'actions avant et après la publication d'une nouvelle version de votre logiciel.
* [unleash](https://github.com/netflix/unleash): Un outil pour automatiser le versioning d'un logiciel et du cycle de publication.
* [lerna](https://github.com/lerna/lerna): Un outil de gestion de monorepos, qui a grandi du projet Babel.
## Outils pour Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Un outil conçu pour créer des messages de commite en suivant les spécifications de Conventional Commits.
Configurable et utilisable pour les projets PHP en tant que dépendance composer ou utilisable globalement pour les projets non-PHP.
* [conform](https://github.com/autonomy/conform): Un outil qui peut être utilisé pour appliquer des stratégies sur les référentiels git, y compris les commites classiques.
## Projets Utilisant Conventional Commits
* [yargs](https://github.com/yargs/yargs): Le parseur d'arguments en ligne de commande sur le thème des pirates préféré de tous.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): une collection d'outils open-source
et bibliothèques pour ajouter une couverture de test à vos tests JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Le versioning automatique et la gestion de CHANGELOG, en utilisant le nouveau bouton squash de GitHub et le flux de travail Conventional Commits recommandé.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) et [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Amélioration optionnelle de l'interface utilisateur [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Une bibliothèque d'accès aux données pour Node et PostgreSQL.
* [electron](https://github.com/electron/electron): Créez des applications de bureau multiplates-formes avec JavaScript, HTML et CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un utilitaire de défilement simple à utiliser pour le centrage des éléments et des animations fluides.
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free d'outilsmodulaire open source.
* [Monica](https://github.com/monicahq/monica): Un système de gestion de relations personnelles open source.
* [Formulaires Nintex](https://www.nintex.fr/plateforme-de-processus/#forms): Créez facilement des formulaires en ligne dynamiques pour capturer et soumettre des données précises et actuelles.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_envie d'avoir votre projet sur cette liste?_ [envoyer une pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

61
content/v1.0.0-beta.3/index.hy.md
View File

@ -214,64 +214,3 @@ API-ում) ՊԵՏՔ Է (MUST) հետևեն `BREAKING CHANGE: ` պիտակին։
կարող է մաքրել պատմությունը մինչև «mergе» անելը և ուշադրություն չդարձնել այդ ամենին։
Սովորաբար git֊ը ավտոմատ «squash» է անում «commit»֊ները PR֊ի ժամանակ և վերջին
«commit»֊ը անում է նախագծի ղեկավարը։
## Սպեցիֆիկացիայի Մասին
Համաձայնեցված «commit»֊ների սպեցիֆիկացիան ոգեշնչված է և ստեղծված
[Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)֊ի
հիման վրա։
Առաջին սևագիրը ստեղծվել է մի քանի մասնակիցների օգնությամբ։
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)․
գործիքների խումբ է, git֊ի պատմությունից hամաձայնեցված «commit»֊ները
առանձնացնելու համար։
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message)․
ծրագիր է, որը «commit»֊ից առանձնացնում է
`{ header: { type, scope, subject }, body, footer }` օբյեկտ:
* [bumped](https://bumped.github.io/)․ գործիք է, որի միջոցով կարելի է, որոշակի
գործողություններ կատարել ծրագրային ապահովումը հրապարակելուց առաջ կամ հետո։
* [unleash](https://github.com/netflix/unleash)․ գործիք, որը ավտոմատացնում է
ծրագրերի թողարկումը և հրապարակումը։
* [lerna](https://github.com/lerna/lerna)․ մոնո֊ռեպոզիտորիաների կառավարման
գործիք է, որը ստեղծվել է Babel֊ի հիման վրա։
## Գործիքներ՝ համածայնեցված «commit»֊ների համար
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen)․ գործիք,
որի միջոցով կարելի է ստեղծել «commit»֊ներ՝ համաձայնեցված «commit»֊ների
սպեցիֆիկացիային համաձայն։ Կարելի է օգտագործել PHP֊ով իրականացվող նախագծերում,
կամ առանձին։
* [conform](https://github.com/autonomy/conform)․ այս գործիքի միջոցով կարելի է
կազմակերպել կանոններ git ռեպոզիտորիաների համար, օրինակ համաձայնեցված
«commit»֊ների հիման վրա։
## Նախագծեր, որոնք օգտագործում են Համաձայնեցված «Commit»֊ներ
* [yargs](https://github.com/yargs/yargs)․ Բոլոր կողմից սիրված «command line»
արգումենտներ առանձնացնելու գործիք (parser)։
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)․ Բաց կոդով գրադարանների
և գործիքների խումբ է, ձեր «JavaScript»֊ով ստեղծված ծրագրային ապահովման տեստերի
ընդգրկելիությունը որոշելու համար։
* [standard-version](https://github.com/conventional-changelog/standard-version):
Ավտոմատ տարբերակման և փոփոխությունների լոգի ստեղծում համաձայնեցված «commit»֊ների
հիման վրա։
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) և
[uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)․
[Apereo uPortal](https://www.apereo.org/projects/uportal)֊ի համար նախատեսված
UI֊ը բարելավելու գործիքներ։
* [massive.js](https://github.com/dmfay/massive-js)․ Տվյալների հետ աշխատելու
համար նախատեսված գրադարան Node֊ի և PostgreSQL֊ի համար։
* [electron](https://github.com/electron/electron)․ Քրոս֊պլատֆորմ, համակարգչային
ծրագրերի ստեղծման համար JavaScript, HTML, և CSS֊ով։
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility)․ Անիմացիաների և
էլեմենտները տեղակայելու համար նախատեսված գործիք։
* [Blaze UI](https://github.com/BlazeUI/blaze)․ UI հավաքելու գործիք։
* [Monica](https://github.com/monicahq/monica): An open source personal
relationship management system.
* [mhy](https://mhy.js.org): A zero-config, out-of-the-box, multi-purpose
toolbox and development environment.
[![Համաձայնեցված «commit»֊ներ](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_Ցանկանու՞մ եք տեսնել ձեր նախագիծը այս ցուցակում_ [ուղղարկեք «pull» հարցում](https://github.com/conventional-changelog/conventionalcommits.org/pulls)։

36
content/v1.0.0-beta.3/index.it.md
View File

@ -148,39 +148,3 @@ Non è la fine del mondo se un commit non segue la specifica Commit Convenzional
### Devono tutti i contributori seguire la specifica Commit Convenzionali?
No. Se usi un workflow basato sugli squash di Git, i mantenitori possono pulire i messaggi dei commit mentre vengono inseriti nel branch principale (merge), non aggiungendo alcun carico di lavoro ai committer occasionali. Un workflow comune è quello di unire (con lo squash) automaticamente i commit dalle pull request e far utilizzare un form ai mantenitori per riscrivere un messaggio più adeguato.
## A proposito
La specifica Commit Convenzionali è ispirata e fortemente basata su [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
La prima bozza di questa specifica è stata scritta in collaborazione con alcuni contributori di:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un set di tool per analizzare messagi dei commit convenzionali dalla cronologia git.
* [bumped](https://bumped.github.io): un tool per il rilascio di software il quale rende più semplice eseguire azioni prima o dopo il rilascio di una versione del vostro software.
* [unleash](https://github.com/netflix/unleash): un tool per automatizzare rilasci e cicli di pubblicazioni di un software.
* [lerna](https://github.com/lerna/lerna): un tool per la gestione di monorepos, nato del progetto Babel.
## Strumenti per Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): un tool realizzato per creare dei messaggi che si basano sulla specifica Conventional Commits.
Totalmente configurabile ed eè utilizzabile per progetti PHP installandola come dipendenza locale o globale per progetti non basati su PHP.
* [conform](https://github.com/autonomy/conform): un tool che può essere usato per introdurre regole sui repository basasti su git, includendo conventional commits.
## Progetti che usano Commit Convenzionali
* [yargs](https://github.com/yargs/yargs): Parser di argomenti da CLI, a tema pirati.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Tool per analizzare i messaggi dei commit e creare oggetti simili a `{ header: { type, scope, subject }, body, footer }`.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): Una collezione di strumenti e librerie open source per aggiungere la coverage dei test JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatizza il versionamento e la gestione del CHANGELOG utilizzando il nuovo pulsante squash di GitHub e il flusso di lavoro consigliato da Commit Convenzionali.
* [massive.js](https://github.com/dmfay/massive-js): un DBAL per Node e PostgreSQL.
* [electron](https://github.com/electron/electron): Realizza app desktop cross platform utilizzando JavaScript, HTML e CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un package dal semplice utilizzo per centrare elementi e animazioni fluide.
* [Blaze UI](https://github.com/BlazeUI/blaze): Set di tool open source per UI.
* [Monica](https://github.com/monicahq/monica): Una piattaforma open source per gestire relazioni.
* [mhy](https://mhy.js.org): 🧩 Un set di tool per l'ambiente di sviluppo senza configurazione.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_vuoi aggingere il tuo progetto alla lista?_ [invia una pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

36
content/v1.0.0-beta.3/index.md
View File

@ -141,39 +141,3 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About
The Conventional Commit specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
The first draft of this specification has been written in collaboration with some of the folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a set of tools for parsing conventional commit messages from git histories.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Spec compliant parsing utility to get object like `{ header: { type, scope, subject }, body, footer }` from given commit message string.
* [bumped](https://bumped.github.io): a tool for releasing software that makes it easy to perform actions before and after releasing a new version of your software.
* [unleash](https://github.com/netflix/unleash): a tool for automating the software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out of the Babel project.
## Tooling for Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): a tool built to create commit messages following the Conventional Commit specs.
Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [conform](https://github.com/autonomy/conform): a tool that can be used to enforce policies on git repositories, including conventional commits.
## Projects Using Conventional Commits
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools and libraries for adding test coverage to your JavaScript tests.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) and [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optional supplemental user interface enhancing [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): A data access library for Node and PostgreSQL.
* [electron](https://github.com/electron/electron): Build cross-platform desktop apps with JavaScript, HTML, and CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): A simple to use scroll utility package for centering elements, and smooth animations
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free open source UI toolkit.
* [Monica](https://github.com/monicahq/monica): An open source personal relationship management system.
* [mhy](https://mhy.js.org): 🧩 A zero-config, out-of-the-box, multi-purpose toolbox and development environment.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

50
content/v1.0.0-beta.3/index.ru.md
View File

@ -169,53 +169,3 @@ Commit'ы с `BREAKING CHANGE` в теле или подвале, не зави
историю всех предыдущих commit'ов при их слияния, не добавляя рабочей нагрузки на случайные commit'ы. Обычно,
рабочий процесс строится на том, что ваша система Git автоматически объединяет (squash) все предыдущие commit'ы пред
перед pull-запросом и предоставляет форму сопровождающему проекта для ввода нового commit'а.
## О спецификации
Conventional Commit вдохновлены и основаны на
[Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
Первый черновик спецификации был написан в сотрудничестве с некоторыми участниками:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): набор утилит для парсинга
стандартных сообщений commit'ов из истории git.
* [bumped](https://bumped.github.io): утилита для релиза приложений, которая позволяет легко выполнять действия
до и после релиза новой версии ваших приложений.
* [unleash](https://github.com/netflix/unleash): утилита для автоматического релиза и публикации приложений.
* [lerna](https://github.com/lerna/lerna): утилита для управления моно-репозиториями, которая выросла и проекта Babel.
Первый черновик спецификации был написан в сотрудничестве с некоторыми участниками:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): набор утилит для парсинга
стандартных сообщений commit'ов из истории git.
* [bumped](https://bumped.github.io): утилита для релиза приложений, которая позволяет легко выполнять действия
до и после релиза новой версии ваших приложений.
* [unleash](https://github.com/netflix/unleash): утилита для автоматического релиза и публикации приложений.
* [lerna](https://github.com/lerna/lerna): утилита для управления моно-репозиториями, которая выросла и проекта Babel.
## Утилиты для Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): утилита для создания сообщений commit'ов, следующих Conventional Commit спецификации.
Используется для PHP-проектов, как зависимость composer, или глобально для не PHP-проектов.
* [conform](https://github.com/autonomy/conform): утилита, которая может быть использована для реализации политик в git-репозиториях, включая правила написания commit'ов.
* [standard-version](https://github.com/conventional-changelog/standard-version): утилита, для автоматический контроля версий и CHANGELOG'ов,
использующая новую кнопку `Squash` GitHub'а. Рекомендует использовать Conventional Commits в рабочем процессе.
## Проекты, использующие Conventional Commits
* [yargs](https://github.com/yargs/yargs): всеми любимый парсер параметров командной строки.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): коллекция утилит и библиотек с открытым исходным кодом для оценки покрытия
тестами вашего кода.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) и [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame):
новый дополнительный пользовательский интерфейс [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): библиотека для доступа к данным PostrgeSQL для Node.
* [electron](https://github.com/electron/electron): утилита для создания крос-платформенных приложений на JavaScript, HTM и CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): простая в использовании утилита контроля прокрутки центральных
элементов и плавной анимации.
* [Blaze UI](https://github.com/BlazeUI/blaze): независимы от фреймворктов набор UI.
* [Monica](https://github.com/monicahq/monica): свободный менеджер персональных связей.
* [mhy](https://mhy.js.org): набор инструментов и окружение для разработки с нулевой конфигурацией, котовое работать из коробки.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_Хотите, чтоб ваш проект появился в этом списке?_ [Отправьте Pull Request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

33
content/v1.0.0-beta.3/index.zh-hans.md
View File

@ -137,36 +137,3 @@ fixes issue #12
并不！如果你使用基于 squash 的 Git 工作流，主管维护者可以在合并时清理提交信息——这不会对普通提交者产生额外的负担。
有种常见的工作流是让 git 系统自动从 pull request 中 squash 出提交，并向主管维护者提供一份表单，用以在合并时输入合适的 git 提交信息。
## 关于
约定式提交规范受到了 [Angular 提交准则](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)的启发，并在很大程度上以其为依据。
该规范的首个草案来自下面这些项目中若干贡献者们的协作：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)：一套从 git 历史中解析出约定式提交说明的工具。
* [bumped](https://bumped.github.io)：一个用于发布软件的工具，可以在为你的软件发布新版本前后轻松地执行操作。
* [unleash](https://github.com/netflix/unleash)：一个用于自动化软件发行和发布生命周期的工具。
* [lerna](https://github.com/lerna/lerna)：一个用于管理宏仓库（monorepo）的工具，源自 Babel 项目。
## 用于约定式提交的工具
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen)：一个用于创建遵循约定式提交规范提交信息的工具。
可配置，并且可以作为 composer 依赖项用于 PHP 项目，或可在非 PHP 项目中全局使用。
* [conform](https://github.com/autonomy/conform)：一个可用以在 git 仓库上施加配置的工具，包括约定式提交。
## 使用约定式提交的项目
* [yargs](https://github.com/yargs/yargs)：广受欢迎的命令行参数解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)：一套为 JavaScript 测试生成测试覆盖率的开源工具和类库。
* [standard-version](https://github.com/conventional-changelog/standard-version) 基于 GitHub 的新 squash 按钮与推荐的约定式提交工作流，自动管理版本和 CHANGELOG。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 和 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)：用于增强 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可选用户界面。
* [massive.js](https://github.com/dmfay/massive-js)：一个用于 Node 和 PostgreSQL 的数据访问类库。
* [electron](https://github.com/electron/electron)：用 JavaScript、HTML 和 CSS 构建跨平台应用。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility)：一个居中元素和平滑动画的滚屏工具包实例。
* [Blaze UI](https://github.com/BlazeUI/blaze)：无框架开源 UI 套件。
* [Monica](https://github.com/monicahq/monica)：一个开源的人际关系管理系统。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想让你的项目出现在上面吗？_ [提交 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

37
content/v1.0.0-beta.4/index.fr.md
View File

@ -158,40 +158,3 @@ Dans le pire des cas, ce n'est pas la fin du monde si un commit atterrit sans re
Non! Si vous utilisez un flux de travail basé sur squash sur Git, les responsables principaux peuvent nettoyer les messages des commits au fur et à mesure de leur fusion, ce qui permet de ne pas ajouter de charge de travail aux committers occasionnels.
Un processus courant consiste à ce que votre système git écrase automatiquement les commits d'une demande d'extraction et présente un formulaire permettant au responsable de la maintenance d'entrer le message du commit git approprié pour la fusion.
## À Propos
La spécification Conventional Commits s’inspire largement de [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) et s’appuie fortement sur celles-ci.
La première version de ces spécifications a été rédigée en collaboration avec certains des les gens qui contribuent à:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): Un ensemble d'outils permettant d'analyser les messages des commits classiques à partir des historiques git.
* [bumped](https://bumped.github.io): Un outil de publication de logiciel qui facilite l'exécution d'actions avant et après la publication d'une nouvelle version de votre logiciel.
* [unleash](https://github.com/netflix/unleash): Un outil pour automatiser le versioning d'un logiciel et du cycle de publication.
* [lerna](https://github.com/lerna/lerna): Un outil de gestion de monorepos, qui a grandi du projet Babel.
## Outils pour Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Un outil conçu pour créer des messages de commit en suivant les spécifications de Conventional Commits.
Configurable et utilisable pour les projets PHP en tant que dépendance composer ou utilisable globalement pour les projets non-PHP.
* [conform](https://github.com/autonomy/conform): Un outil qui peut être utilisé pour appliquer des stratégies sur les référentiels git, y compris les commits classiques.
* [standard-version](https://github.com/conventional-changelog/standard-version): Le versioning automatique et la gestion de CHANGELOG, en utilisant le nouveau bouton squash de GitHub et le flux de travail Conventional Commits est recommandé.
## Projets Utilisant Conventional Commits
* [yargs](https://github.com/yargs/yargs): Le parseur d'arguments en ligne de commande sur le thème des pirates préféré de tous.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): une collection d'outils open-source
et bibliothèques pour ajouter une couverture de test à vos tests JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Le versioning automatique et la gestion de CHANGELOG, en utilisant le nouveau bouton squash de GitHub et le flux de travail Conventional Commits recommandé.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) et [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Amélioration optionnelle de l'interface utilisateur [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Une bibliothèque d'accès aux données pour Node et PostgreSQL.
* [electron](https://github.com/electron/electron): Créez des applications de bureau multiplates-formes avec JavaScript, HTML et CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un utilitaire de défilement simple à utiliser pour le centrage des éléments et des animations fluides.
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free d'outilsmodulaire open source.
* [Monica](https://github.com/monicahq/monica): Un système de gestion de relations personnelles open source.
* [mhy](https://mhy.js.org): 🧩 Une boîte à outils polyvalente et un environnement de développement prêts à l'emploi.
* [Formulaires Nintex](https://www.nintex.fr/plateforme-de-processus/#forms): Créez facilement des formulaires en ligne dynamiques pour capturer et soumettre des données précises et actuelles.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_envie d'avoir votre projet sur cette liste?_ [envoyer une pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

64
content/v1.0.0-beta.4/index.hy.md
View File

@ -230,67 +230,3 @@ _ՄԱՐՄԻՆԻ_ կամ _ՆԵՐՔԵՎԻ ՀԱՏՎԱԾԻ_ սկզբում, եթե
կարող է մաքրել պատմությունը մինչև «mergе» անելը և ուշադրություն չդարձնել այդ ամենին։
Սովորաբար git֊ը ավտոմատ «squash» է անում «commit»֊ները PR֊ի ժամանակ և վերջին
«commit»֊ը անում է նախագծի ղեկավարը։
## Սպեցիֆիկացիայի Մասին
Համաձայնեցված «commit»֊ների սպեցիֆիկացիան ոգեշնչված է և ստեղծված
[Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)֊ի
հիման վրա։
Առաջին սևագիրը ստեղծվել է մի քանի մասնակիցների օգնությամբ։
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)․
գործիքների խումբ է, git֊ի պատմությունից hամաձայնեցված «commit»֊ները
առանձնացնելու համար։
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message)․
ծրագիր է, որը «commit»֊ից առանձնացնում է
`{ header: { type, scope, subject }, body, footer }` օբյեկտ:
* [bumped](https://bumped.github.io/)․ գործիք է, որի միջոցով կարելի է, որոշակի
գործողություններ կատարել ծրագրային ապահովումը հրապարակելուց առաջ կամ հետո։
* [unleash](https://github.com/netflix/unleash)․ գործիք, որը ավտոմատացնում է
ծրագրերի թողարկումը և հրապարակումը։
* [lerna](https://github.com/lerna/lerna)․ մոնո֊ռեպոզիտորիաների կառավարման
գործիք է, որը ստեղծվել է Babel֊ի հիման վրա։
## Գործիքներ՝ համածայնեցված «commit»֊ների համար
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen)․ գործիք,
որի միջոցով կարելի է ստեղծել «commit»֊ներ՝ համաձայնեցված «commit»֊ների
սպեցիֆիկացիային համաձայն։ Կարելի է օգտագործել PHP֊ով իրականացվող նախագծերում,
կամ առանձին։
* [conform](https://github.com/autonomy/conform)․ այս գործիքի միջոցով կարելի է
կազմակերպել կանոններ git ռեպոզիտորիաների համար, օրինակ համաձայնեցված
«commit»֊ների հիման վրա։
* [standard-version](https://github.com/conventional-changelog/standard-version):
Ավտոմատ տարբերակման և փոփոխությունների լոգի ստեղծում համաձայնեցված «commit»֊ների
հիման վրա։
* [commitsar](https://github.com/commitsar-app/commitsar): Go լեզվով գրված
գործիք, որը ստուգում է, արդյոք «commit»֊ը համապատասխանում է համաձայնեցված
«commit»֊ների սպեցիֆիկացիային։ Կարելի է օգտագործել Docker֊ի հետ։
## Նախագծեր, որոնք օգտագործում են Համաձայնեցված «Commit»֊ներ
* [yargs](https://github.com/yargs/yargs)․ Բոլոր կողմից սիրված «command line»
արգումենտներ առանձնացնելու գործիք (parser)։
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)․ Բաց կոդով գրադարանների
և գործիքների խումբ է, ձեր «JavaScript»֊ով ստեղծված ծրագրային ապահովման տեստերի
ընդգրկելիությունը որոշելու համար։
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) և
[uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)․
[Apereo uPortal](https://www.apereo.org/projects/uportal)֊ի համար նախատեսված
UI֊ը բարելավելու գործիքներ։
* [massive.js](https://github.com/dmfay/massive-js)․ Տվյալների հետ աշխատելու
համար նախատեսված գրադարան Node֊ի և PostgreSQL֊ի համար։
* [electron](https://github.com/electron/electron)․ Քրոս֊պլատֆորմ, համակարգչային
ծրագրերի ստեղծման համար JavaScript, HTML, և CSS֊ով։
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility)․ Անիմացիաների և
էլեմենտները տեղակայելու համար նախատեսված գործիք։
* [Blaze UI](https://github.com/BlazeUI/blaze)․ UI հավաքելու գործիք։
* [Monica](https://github.com/monicahq/monica): An open source personal
relationship management system.
* [mhy](https://mhy.js.org): A zero-config, out-of-the-box, multi-purpose
toolbox and development environment.
[![Համաձայնեցված «commit»֊ներ](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_Ցանկանու՞մ եք տեսնել ձեր նախագիծը այս ցուցակում_ [ուղղարկեք «pull» հարցում](https://github.com/conventional-changelog/conventionalcommits.org/pulls)։

37
content/v1.0.0-beta.4/index.id.md
View File

@ -153,40 +153,3 @@ Dalam skenario terburuk, ini bukan akhir dunia jika komit mendarat yang tidak me
Tidak! Jika Anda menggunakan alur kerja berbasis squash di pengelola Git dapat membersihkan pesan komit saat mereka digabung — menambahkan tidak ada beban kerja ke komuter biasa.
Alur kerja umum untuk ini adalah membuat sistem git Anda secara otomatis squash melakukan dari permintaan tarikan dan menyajikan formulir bagi pengelola utama untuk memasukkan pesan git commit yang tepat untuk penggabungan.
## About
Spesifikasi Conventional Commit terinspirasi oleh, dan didasarkan pada, [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
Draf pertama spesifikasi ini telah ditulis bersama dengan beberapa orang yang berkontribusi pada:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): seperangkat alat untuk mem-parsing pesan komit konvensional dari riwayat git.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Utilitas penguraian yang sesuai dengan spesifikasi untuk mendapatkan objek seperti `{ header: { type, scopre, subject }, body, footer }` dari string pesan komit yang diberikan.
* [bumped](https://bumped.github.io): alat untuk merilis perangkat lunak yang memudahkan untuk melakukan tindakan sebelum dan sesudah merilis versi baru perangkat lunak Anda.
* [unleash](https://github.com/netflix/unleash): alat untuk mengotomatiskan rilis perangkat lunak dan siklus penerbitan.
* [lerna](https://github.com/lerna/lerna): alat untuk mengelola monorepos, yang tumbuh dari proyek Babel.
## Alat untuk Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen):
alat yang dibuat untuk membuat pesan komit mengikuti spesifikasi Komitmen Konvensional.
Dapat dikonfigurasi dan digunakan untuk proyek PHP sebagai dependensi komposer atau dapat digunakan secara global untuk proyek non-PHP.
* [conform](https://github.com/autonomy/conform): alat yang dapat digunakan untuk menerapkan repositori, termasuk conventional commits.
* [standard-version](https://github.com/conventional-changelog/standard-version): Versi otomatis dan manajemen CHANGELOG, menggunakan tombol squash baru GitHub dan alur kerja Conventional Commits yang direkomendasikan.
## Proyek Menggunakan Komitmen Konvensional
* [yargs](https://github.com/yargs/yargs): parser argumen baris perintah bertema bajak laut favorit semua orang.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): koleksi alat dan pustaka sumber terbuka untuk menambahkan cakupan tes ke tes JavaScript Anda.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) dan [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Opsi peningkatan antarmuka pengguna tambahan [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Pustaka akses data untuk Node dan PostgreSQL.
* [electron](https://github.com/electron/electron): Bangun aplikasi desktop lintas platform dengan JavaScript, HTML, dan CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Paket utilitas gulir yang mudah digunakan untuk elemen pemusatan, dan animasi yang halus
* [Blaze UI](https://github.com/BlazeUI/blaze): Kerangka kerja perangkat UI sumber bebas terbuka.
* [Monica](https://github.com/monicahq/monica): Sumber Terbuka sistem manajemen hubungan pribadi.
* [mhy](https://mhy.js.org): 🧩 Toolbox nol-konfigurasi, out-of-the-box, multiguna dan lingkungan pengembangan.
* [Formulir Nintex](https://www.nintex.com/workflow-automation/modern-forms/): Membuat formulir online dinamis dengan mudah untuk menangkap dan mengirimkan data yang akurat dan terkini.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_ingin proyek Anda ada dalam daftar ini?_ [kirimkan pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

36
content/v1.0.0-beta.4/index.it.md
View File

@ -156,39 +156,3 @@ Non è la fine del mondo se un commit non segue la specifica Commit Convenzional
### Devono tutti i contributori seguire la specifica Commit Convenzionali?
No. Se usi un workflow basato sugli squash di Git, i mantenitori possono pulire i messaggi dei commit mentre vengono inseriti nel branch principale (merge), non aggiungendo alcun carico di lavoro ai committer occasionali. Un workflow comune è quello di unire (con lo squash) automaticamente i commit dalle pull request e far utilizzare un form ai mantenitori per riscrivere un messaggio più adeguato.
## A proposito
La specifica Commit Convenzionali è ispirata e fortemente basata su [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
La prima bozza di questa specifica è stata scritta in collaborazione con alcuni contributori di:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un set di tool per analizzare messagi dei commit convenzionali dalla cronologia git.
* [bumped](https://bumped.github.io): un tool per il rilascio di software il quale rende più semplice eseguire azioni prima o dopo il rilascio di una versione del vostro software.
* [unleash](https://github.com/netflix/unleash): un tool per automatizzare rilasci e cicli di pubblicazioni di un software.
* [lerna](https://github.com/lerna/lerna): un tool per la gestione di monorepos, nato del progetto Babel.
## Strumenti per Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): un tool realizzato per creare dei messaggi che si basano sulla specifica Conventional Commits.
Totalmente configurabile ed eè utilizzabile per progetti PHP installandola come dipendenza locale o globale per progetti non basati su PHP.
* [conform](https://github.com/autonomy/conform): un tool che può essere usato per introdurre regole sui repository basasti su git, includendo conventional commits.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatizza il versionamento e la gestione del CHANGELOG utilizzando il nuovo pulsante squash di GitHub e il flusso di lavoro consigliato da Commit Convenzionali.
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): offre completamento estensibile basato sul contesto o su template, ed ispezioni, per Conventional Commits all'interno del dialogo di commit per il VCS configurato. Disponibile per tutti gli [IDE JetBrains](https://www.jetbrains.com/).
## Progetti che usano Commit Convenzionali
* [yargs](https://github.com/yargs/yargs): Parser di argomenti da CLI, a tema pirati.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Tool per analizzare i messaggi dei commit e creare oggetti simili a `{ header: { type, scope, subject }, body, footer }`.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): Una collezione di strumenti e librerie open source per aggiungere la coverage dei test JavaScript.
* [massive.js](https://github.com/dmfay/massive-js): un DBAL per Node e PostgreSQL.
* [electron](https://github.com/electron/electron): Realizza app desktop cross platform utilizzando JavaScript, HTML e CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un package dal semplice utilizzo per centrare elementi e animazioni fluide.
* [Blaze UI](https://github.com/BlazeUI/blaze): Set di tool open source per UI.
* [Monica](https://github.com/monicahq/monica): Una piattaforma open source per gestire relazioni.
* [mhy](https://mhy.js.org): 🧩 Un set di tool per l'ambiente di sviluppo senza configurazione.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_vuoi aggingere il tuo progetto alla lista?_ [invia una pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

35
content/v1.0.0-beta.4/index.ja.md
View File

@ -178,38 +178,3 @@ SemVerを使用して、この仕様に対する独自の拡張仕様をリリ
いいえ！ Gitでsquashベースのワークフローを使用するなら、主要メンテナはマージ時にコミットメッセージをクリーンアップすることができるため、通常のコミッタには作業負荷がかかりません。
また一般的なワークフローの場合は、あなたのgitシステムが自動的にpull requestからコミットを破棄し、主要メンテナにマージのための適切なgit commitメッセージを入力するためのフォームを提示することです。
## 要約
Conventional Commitの仕様は、[Angular Commitのガイドライン](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)に触発されており、それに基づいています。
この仕様書の最初のドラフトは、以下に何人かのコントリビューターと共同して書かれました:
* [traditional-changelog](https://github.com/conventional-changelog/conventional-changelog): git履歴からconventional commitのメッセージを変換するためのツールのセット。
* [bumped](https://bumped.github.io): ソフトウェアの新しいバージョンをリリースする前後にアクションを実行することを手助けするためのツール。
* [unleash](https://github.com/netflix/unleash): ソフトウェアのリリースを自動化し、ライフサイクルを公開するためのツール。
* [lerna](https://github.com/lerna/lerna): Babelプロジェクトから生まれたモノレポを管理するためのツール。
## Conventional Commitsのためのツール一覧
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Conventional Commit の仕様に従ってコミットメッセージを作成するためのツール。
composerに依存するPHPプロジェクトに対して設定、使用可能であり、非PHPプロジェクトに対してもグローバルに使用可能。
* [conform](https://github.com/autonomy/conform): conventional commitsを含めたgitリポジトリにポリシーを強制するために使用できるツール。
* [standard-version](https://github.com/conventional-changelog/standard-version): GitHubの新しいsquashボタンと推奨されているConventional Commitワークフローを使用した、自動のバージョン管理とCHANGELOG管理。
## Conventional Commitsを利用しているプロジェクト
* [yargs](https://github.com/yargs/yargs): 多くの人に人気な海賊をテーマにしたコマンドライン引数パーサ。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): JavaScriptテストにテストのカバレッジを追加するためのオープンソースのツールとライブラリのコレクション。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) と [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): 追加の[Apereo uPortal](https://www.apereo.org/projects/uportal)でユーザーインターフェースを強化できます。
* [massive.js](https://github.com/dmfay/massive-js): NodeとPostgreSQL用のデータアクセスライブラリ。
* [electron](https://github.com/electron/electron): JavaScript、HTML、およびCSSを使用してクロスプラットフォームのデスクトップアプリケーションを構築します。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): 要素のセンタリング、スムーズなスクロールアニメーションを簡単に実現するためのスクロールユーティリティパッケージです。
* [Blaze UI](https://github.com/BlazeUI/blaze): フレームワークに依存しないオープンソースUIツールキット。
* [Monica](https://github.com/monicahq/monica): オープンソースの人的関係管理システム。
* [mhy](https://mhy.js.org): 🧩 設定不要ですぐに使える多目的ツールボックスおよび開発環境。
* [Nintex fōmuzu](https://www.nintex.jp/process-platform/#forms): 動的なオンラインフォームを簡単に作成して、正確で最新のデータをキャプチャして送信します。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_あなたのプロジェクトをこのリストに載せたいですか？_ [プルリクエストを送ってください](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

33
content/v1.0.0-beta.4/index.ko.md
View File

@ -140,36 +140,3 @@ SemVer를 사용해서 이 규격에 대한 사용자 자신의 확장판을 릴
아니요! Git를 기반으로 스쿼시를 사용하는 경우, 리드 유지관리자는 커밋된 메시지를 병합할 때 정리할 수 있으므로 일반 커밋자에 작업량이 추가되지 않습니다.
이에 대한 일반적인 작업 흐름은 Git 시스템이 자동으로 풀 요청에서 커밋되도록 하고 리드 유지관리자가 병합에 대한 적절한 Git 커밋 메시지를 입력할 수 있는 양식을 제시하도록 하는 것입니다.
## About
Conventional Commits 규격은 [앵귤러 커밋 가이드라인](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)에서 영감을 받았으며 이를 토대로 하고 있습니다.
이 규격의 첫 번째 초안은 아래 언급된 프로젝트에 기여하고 있는 분들과의 협업으로 작성되었습니다:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): Git 히스토리에서 conventional commit 메시지를 구문 분석하기 위한 도구 모음.
* [bumped](https://bumped.github.io): 소프트웨어의 새 버전을 릴리즈하기 전후에 작업을 쉽게 수행할 수 있는 소프트웨어를 릴리즈하기 위한 도구.
* [unleash](https://github.com/netflix/unleash): 소프트웨어 릴리즈 및 배포 수명 주기를 자동화하기 위한 도구.
* [lerna](https://github.com/lerna/lerna): Babel 프로젝트에서 성장한 monorepo를 관리 도구.
## Conventional Commits를 위한 도구
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Conventional Commits 규격에 따라 커밋 메시지를 생성하기 위해 사용되는 도구로 PHP 프로젝트에서 컴포저 의존성으로 구성 및 사용할 수 있거나 PHP 이외의 프로젝트에서 전 세계적으로 사용할 수 있습니다.
* [conform](https://github.com/autonomy/conform): Conventional Commits를 포함한 git 저장소에서 정책을 강제하는데 사용되는 도구.
* [standard-version](https://github.com/conventional-changelog/standard-version): GitHub의 스쿼시 버튼과 Conventional Commits 워크플로우를 이용한 자동 버전 지정 및 CHANGELOG 관리
## Conventional Commits를 이용하고 있는 프로젝트
* [yargs](https://github.com/yargs/yargs): 모두가 가장 좋아하는 해적 테마의 커맨드 라인 인자 구문 분석기.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): 자바스크립트 테스트에 테스트 적용 범위를 추가하는 오픈 소스 도구 및 라이브러리 모음.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal)와 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): [Apereo uPortal](https://www.apereo.org/projects/uportal)을 향상시켜주는 옵션으로 추가 가능한 사용자 인터페이스.
* [massive.js](https://github.com/dmfay/massive-js): Node와 PostgreSQL을 위한 데이터 접근 라이브러리
* [electron](https://github.com/electron/electron): 자바스크립트, HTML, 그리고 CSS를 이용하여 크로스 클랫폼 데스크탑 앱을 만드는 프레임워크.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): 사용하기 쉬운, 요소 중앙 정렬 및 부드러운 애니메이션을 위한 스크롤 유틸리티 패키지.
* [Blaze UI](https://github.com/BlazeUI/blaze): 프레임워크가 필요 없는 오픈소스 UI 툴킷.
* [Monica](https://github.com/monicahq/monica): 오픈 소스 개인 관계 관리 시스템.
* [mhy](https://mhy.js.org): 🧩 설정이 필요 없고 바로 사용 가능한 다목적 툴 박스와 개발 환경
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_위의 목록에 여러분의 프로젝트를 남기고 싶으세요??_ [PR을 만들어보세요](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

38
content/v1.0.0-beta.4/index.md
View File

@ -153,41 +153,3 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About
The Conventional Commit specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
The first draft of this specification has been written in collaboration with some of the folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a set of tools for parsing conventional commit messages from git histories.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Spec compliant parsing utility to get object like `{ header: { type, scope, subject }, body, footer }` from given commit message string.
* [bumped](https://bumped.github.io): a tool for releasing software that makes it easy to perform actions before and after releasing a new version of your software.
* [unleash](https://github.com/netflix/unleash): a tool for automating the software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out of the Babel project.
## Tooling for Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): a tool built to create commit messages following the Conventional Commit specs.
Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [conform](https://github.com/autonomy/conform): a tool that can be used to enforce policies on git repositories, including conventional commits.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are conventional commit compliant. Comes with Docker image for CI uses.
## Projects Using Conventional Commits
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools and libraries for adding test coverage to your JavaScript tests.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) and [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optional supplemental user interface enhancing [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): A data access library for Node and PostgreSQL.
* [electron](https://github.com/electron/electron): Build cross-platform desktop apps with JavaScript, HTML, and CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): A simple to use scroll utility package for centering elements, and smooth animations
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free open source UI toolkit.
* [Monica](https://github.com/monicahq/monica): An open source personal relationship management system.
* [mhy](https://mhy.js.org): 🧩 A zero-config, out-of-the-box, multi-purpose toolbox and development environment.
* [sharec](https://github.com/lamartire/sharec): Minimalistic tool for boilerplating and configuration versioning.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

54
content/v1.0.0-beta.4/index.pt-br.md
View File

@ -203,57 +203,3 @@ Não! Se você usar um workflow de git baseado em squash, os mantenedores poder
request e apresente um formulário para o mantenedor inserir a mensagem do commit
apropriada para o merge.
## Sobre
A especificação do Convencional Commits é inspirada e fortemente baseada na
[Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
O primeiro rascunho desta especificação foi escrito em colaboração com algumas
pessoas que contribuem para:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog):
um conjunto de ferramentas para analisar mensagens de commit a partir do histórico git.
* [bumped](https://bumped.github.io): uma ferramenta que facilita o "release" de
software. Facilitando executar ações antes e depois de uma liberar uma nova versão.
* [unleash](https://github.com/netflix/unleash): uma ferramenta para automatizar
o ciclo de "release" e publicação de software.
* [lerna](https://github.com/lerna/lerna): uma ferramenta para gerenciar monorepos,
que surgiu do projeto Babel.
## Ferramentas para Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): uma
ferramenta para criar mensagens de commit seguindo as especificações do
Conventional Commits. Configurável e util para projetos PHP como dependência do
composer ou "global" para projetos não-PHP.
* [conform](https://github.com/autonomy/conform): uma ferramenta que pode ser
usada para garantir "regras" em repositórios git, incluindo o Conventional Commits.
* [standard-version](https://github.com/conventional-changelog/standard-version):
Geração automática de versões e gerenciamento de CHANGELOG, usando o novo botão
de squash do GitHub e o workflow recomendado do Conventional Commits.
## Projetos Utilizando Conventional Commits
* [yargs](https://github.com/yargs/yargs): o parser de argumentos de linha de
comando, com tema de pirata, favorito de todos.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): uma coleção de ferramentas
e bibliotecas de código aberto para adicionar cobertura de teste a seus testes
de JavaScript.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) e
[uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame):
Aperfeiçoamento opcional da interface do usuário [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Uma biblioteca de acesso a
dados para o Node e PostgreSQL.
* [electron](https://github.com/electron/electron): Crie aplicativos desktop
cross-platform com JavaScript, HTML e CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Um pacote
simples de usar para centralizar elementos e animações suaves.
* [Blaze UI](https://github.com/BlazeUI/blaze): UI Toolkit de código aberto, Framework-free.
* [Monica](https://github.com/monicahq/monica): Um CRM pessoal. Lembre-se de
tudo sobre seus amigos e familiares.
* [mhy](https://mhy.js.org): 🧩 Uma toolbox e sistema para desenvolvimento com
zero configuração, pronta para uso, multifuncional.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_quer seu projeto nesta lista?_ [envie um pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

42
content/v1.0.0-beta.4/index.ru.md
View File

@ -185,45 +185,3 @@ Commit'ы с `BREAKING CHANGE` в теле или подвале, независ
историю всех предыдущих commit'ов при их слиянии, не добавляя рабочей нагрузки на случайные commit'ы. Обычно,
рабочий процесс строится на том, что ваша система Git автоматически объединяет (squash) все предыдущие commit'ы
перед pull-запросом и предоставляет форму сопровождающему проекта для ввода нового commit'а.
## О спецификации
Conventional Commits вдохновлены и основаны на
[Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
Первый черновик спецификации был написан в сотрудничестве с некоторыми участниками:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): набор утилит для парсинга
стандартных сообщений commit'ов из истории git.
* [bumped](https://bumped.github.io): утилита для релиза приложений, которая позволяет легко выполнять действия
до и после релиза новой версии ваших приложений.
* [unleash](https://github.com/netflix/unleash): утилита для автоматического релиза и публикации приложений.
* [lerna](https://github.com/lerna/lerna): утилита для управления моно-репозиториями, которая выросла из проекта Babel.
## Утилиты для Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): утилита для создания сообщений commit'ов, следующих Conventional Commits спецификации.
Используется для PHP-проектов, как зависимость composer, или глобально для не PHP-проектов.
* [conform](https://github.com/autonomy/conform): утилита, которая может быть использована для реализации политик в git-репозиториях, включая правила написания commit'ов.
* [standard-version](https://github.com/conventional-changelog/standard-version): утилита, для автоматического контроля версий и CHANGELOG'ов,
использующая новую кнопку `Squash` GitHub'а. Рекомендует использовать Conventional Commits в рабочем процессе.
## Проекты, использующие Conventional Commits
* [yargs](https://github.com/yargs/yargs): всеми любимый парсер параметров командной строки.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): коллекция утилит и библиотек с открытым исходным кодом для оценки покрытия
тестами вашего кода.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) и [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame):
новый дополнительный пользовательский интерфейс [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): библиотека для доступа к данным PostrgeSQL для Node.
* [electron](https://github.com/electron/electron): утилита для создания крос-платформенных приложений на JavaScript, HTM и CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): простая в использовании утилита контроля прокрутки центральных
элементов и плавной анимации.
* [Blaze UI](https://github.com/BlazeUI/blaze): независимы от фреймворктов набор UI.
* [Monica](https://github.com/monicahq/monica): свободный менеджер персональных связей.
* [mhy](https://mhy.js.org): набор инструментов и окружение для разработки с нулевой конфигурацией, которые работают из коробки.
* [sharec](https://github.com/lamartire/sharec): минималистичный инструмент для скаффолдинга и версионирования конфигурации.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_Хотите, чтоб ваш проект появился в этом списке?_ [Отправьте Pull Request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

37
content/v1.0.0-beta.4/index.zh-hans.md
View File

@ -143,40 +143,3 @@ closes issue #12
并不！如果你使用基于 squash 的 Git 工作流，主管维护者可以在合并时清理提交信息——这不会对普通提交者产生额外的负担。
有种常见的工作流是让 git 系统自动从 pull request 中 squash 出提交，并向主管维护者提供一份表单，用以在合并时输入合适的 git 提交信息。
## 关于
约定式提交规范受到了 [Angular 提交准则](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)的启发，并在很大程度上以其为依据。
该规范的首个草案来自下面这些项目中若干贡献者们的协作：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)：一套从 git 历史中解析出约定式提交说明的工具。
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message)：兼容规范的解析工具，可以将给定提交信息的字符串解析成对象，结果形如 `{ header: { type, scope, subject }, body, footer }`。
* [bumped](https://bumped.github.io)：一个用于发布软件的工具，可以在为你的软件发布新版本前后轻松地执行操作。
* [unleash](https://github.com/netflix/unleash)：一个用于自动化软件发行和发布生命周期的工具。
* [lerna](https://github.com/lerna/lerna)：一个用于管理宏仓库（monorepo）的工具，源自 Babel 项目。
## 用于约定式提交的工具
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen)：一个用于创建遵循约定式提交规范提交信息的工具。
可配置，并且可以作为 composer 依赖项用于 PHP 项目，或可在非 PHP 项目中全局使用。
* [conform](https://github.com/autonomy/conform)：一个可用以在 git 仓库上施加配置的工具，包括约定式提交。
* [standard-version](https://github.com/conventional-changelog/standard-version) 基于 GitHub 的新 squash 按钮与推荐的约定式提交工作流，自动管理版本和 CHANGELOG。
* [commitsar](https://github.com/commitsar-app/commitsar)： 一个检查提交信息是否符合约定式提交规范的 Go 语言工具。可在 CI 的 Docker 镜像中使用。
## 使用约定式提交的项目
* [yargs](https://github.com/yargs/yargs)：广受欢迎的命令行参数解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)：一套为 JavaScript 测试生成测试覆盖率的开源工具和类库。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 和 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)：用于增强 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可选用户界面。
* [massive.js](https://github.com/dmfay/massive-js)：一个用于 Node 和 PostgreSQL 的数据访问类库。
* [electron](https://github.com/electron/electron)：用 JavaScript、HTML 和 CSS 构建跨平台应用。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility)：一个居中元素和平滑动画的滚屏工具包实例。
* [Blaze UI](https://github.com/BlazeUI/blaze)：无框架开源 UI 套件。
* [Monica](https://github.com/monicahq/monica)：一个开源的人际关系管理系统。
* [mhy](https://mhy.js.org)：🧩 一个零配置、开箱即用的、多用途工具箱与开发环境。
* [sharec](https://github.com/lamartire/sharec)：一个用于模板和配置文件版本化的极简工具。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想让你的项目出现在上面吗？_ [提交 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

34
content/v1.0.0-beta.4/index.zh-hant.md
View File

@ -145,37 +145,3 @@ closes issue #12
不用！如果你使用的是基於 squash 的 Git 工作流程，主維護者可以在合併時清理提交說明，因此這不會對一般的提交者產生額外的負擔。
有一種常見的工作流程是讓 git 系統自動從 pull request 中 squash 出提交，然後提供一份表單給主維護者，用以在合併的時候輸入合適的 git 提交說明。
## 關於
約定式提交規範，是受到 [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) 的啟發，也很大程度以其為依據。
此規範的第一版草稿，是由以下專案的一些貢獻者所協作出來的：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): 一套用從 git 歷史中解析約定式提交的工具。
* [bumped](https://bumped.github.io): 一個用於發布軟體的工具，讓發布軟體新版本的前後能輕鬆的執行動作。
* [unleash](https://github.com/netflix/unleash): 一個能自動化軟體發布與發行的生命週期的工具。
* [lerna](https://github.com/lerna/lerna): 一個用於管理 monorepos 的工具，源自於 Babel 專案。
## 用於約定式提交的工具
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): 一個用於建立遵循約定式提交規範的提交說明的工具。
可設定且可作為 PHP 專案中 composer 的依賴，或是對非 PHP 的專案中可以全域使用。
* [conform](https://github.com/autonomy/conform): 一個可以對 git repositories 加上規則的工具，包含約定式提交。
* [standard-version](https://github.com/conventional-changelog/standard-version): 基於 GitHub 的新 squash 按鈕與推薦的約定式提交工作流程，自動化版本與 CHANGELOG 管理。
## 使用約定式提交的專案
* [yargs](https://github.com/yargs/yargs): 廣受喜愛的指令參數解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): 一套為 JavaScript 測試加上測試覆蓋率的開源工具與函式庫。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 與 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): 用於增強 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可選使用者介面。
* [massive.js](https://github.com/dmfay/massive-js): 一個用於 Node 與 PostgreSQL 的資料存取函式庫。
* [electron](https://github.com/electron/electron): 用 JavaScript、HTML 與 CSS 建立跨平台的桌面應用程式。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): 一個用於置中元素與平滑動畫的捲動畫面套件。
* [Blaze UI](https://github.com/BlazeUI/blaze): 無框架開源 UI 套件。
* [Monica](https://github.com/monicahq/monica): 一個開源的人際關係管理系統。
* [mhy](https://mhy.js.org): 🧩 一個無需設定、可以直接使用、多用途的工具箱與開發環境。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想讓你的專案出現在列表中嗎？_ [發送 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

20
content/v1.0.0-beta/index.it.md
View File

@ -137,23 +137,3 @@ Semplicemente il commit verrà ignorato dai tool che sono basati su questa speci
No. Se usi un workflow basato sugli squash di Git, i mantenitori possono pulire i messaggi dei commit mentre vengono inseriti nel branch principale (merge), non aggiungendo alcun carico di lavoro ai committer occasionali.
Un workflow comune è quello di unire (con lo squash) automaticamente i commit dalle pull request e far utilizzare un form ai mantenitori per riscrivere un messaggio più adeguato.
## Riguardo
La specifica Commit Convenzionali è ispirata e fortemente basata su [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
La prima bozza di questa specifica è stata scritta in collaborazione con alcuni contributori di:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un set di tool per analizzare messagi dei commit convenzionali dalla cronologia git.
* [unleash](https://github.com/netflix/unleash): un tool per automatizzare rilasci e cicli di pubblicazioni di un software.
* [lerna](https://github.com/lerna/lerna): un tool per la gestione di monorepos, nato del progetto Babel.
## Progetti che usano Commit Convenzionali
* [yargs](https://github.com/yargs/yargs): Parser di argomenti da CLI, a tema pirati.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): Una collezione di strumenti e librerie open source per aggiungere la coverage dei test JavaScript.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatizza il versionamento e la gestione del CHANGELOG utilizzando il nuovo pulsante squash di GitHub e il flusso di lavoro consigliato da Commit Convenzionali.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_vuoi aggingere il tuo progetto alla lista?_ [invia una pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

27
content/v1.0.0-beta/index.md
View File

@ -131,30 +131,3 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
### Do all my contributors need to use the conventional commit specification?
No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
## About
The Conventional Commit specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
The first draft of this specification has been written in collaboration with some of the
folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a
set of tools for parsing conventional commit messages from git histories.
* [unleash](https://github.com/netflix/unleash): a tool for automating the
software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out
of the Babel project.
## Projects Using Conventional Commits
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools
and libraries for adding test coverage to your JavaScript tests.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

21
content/v1.0.0-beta/index.pl.md
View File

@ -131,24 +131,3 @@ Po prostu znaczy to, że będzie pominięty przez narzędzia bazujące na specyf
Nie! Jeśli używasz trybu bazującego na spłaszczaniu historii dostarczeń, wtedy główni opiekunowie projektu mogą posprzątać wiadomości
podczas dostarczania. Takie podejście nie narzuca żadnego obowiązku na osoby dostarczające od czasu do czasu. Powszechnym podejściem
jest używanie automatycznego spłaszczania historii dostarczeń z pull requestóœ oraz wyświetlenie formularza osobie dostarczającej w celu wypełnienia wiadomości poprawną treścią.
## O twórcy
Specyfikacja Konwencjonalnych Commitów jest inspirowana oraz mocno bazuje na [Wytycznych Wiadomości Angulara](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
Pierwsza wersja tej specyfikacji została stworzona we współpracy z kilkoma kontrybutorami takich projektów jak:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): zbiór narzędziprośby wciągnięcia
pozwalających na parsowanie konwencjonalnych commitów z historii `git`owych dostarczeń.
* [unleash](https://github.com/netflix/unleash): narzędzie do automatyzacji wydawania oraz publikowania.
* [lerna](https://github.com/lerna/lerna): narzędzie do zarządzania mono-repozytoriami, które wyrosło z projektu Babel.
## Projekty używające Konwencjonalnych Commitów
* [yargs](https://github.com/yargs/yargs): uwielbiany przez wszystkich, piracko stylizowany parser argumentów linii komend.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): kolekcja otwarto-źródłowych narzędzi oraz bibliotek do dodawania miar pokrycia kodu do Twoich testów jednostkowych
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatyczne zarządzanie wersjami oraz DZIENNIKIEM ZMIAN, używający nowego przycisku Spłaszcz na GitHubie oraz trybu pracy opartego o Konwencjonalne Wiadomości.
[![Konwencjonalne Commity](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_chcesz, aby Twój projekt znajdował się na tej liście?_ [stwórz pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

22
content/v1.0.0-beta/index.zh-hans.md
View File

@ -104,25 +104,3 @@ draft: false
### 所有的贡献者都需要使用约定式提交规范吗？
并不！如果你使用基于 squash 的 Git 工作流，主管维护者可以在合并时清理提交信息——这不会对普通提交者产生额外的负担。有种常见的工作流是让 git 系统自动从 pull request 中 squash 出提交，向主管维护者提供表单，来在合并时输入合适的 git 提交信息。
## 关于
约定式提交规范受到了 [Angular 提交准则](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)的启发，并在很大程度上以其为依据。
该规范的首个草案来自下面这些项目中若干贡献者们的协作：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)：一套从 git 历史中解析出约定式提交说明的工具。
* [unleash](https://github.com/netflix/unleash)：一个用于自动化软件发行和发布生命周期的工具。
* [lerna](https://github.com/lerna/lerna)：一个用于管理宏仓库的工具，源自 Babel 项目。
## 使用约定式提交的项目
* [yargs](https://github.com/yargs/yargs)：广受欢迎的命令行参数解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)：一套为 JavaScript 测试生成测试覆盖率的开源工具和类库。
* [standard-version](https://github.com/conventional-changelog/standard-version) 基于 GitHub 的新 squash 按钮与推荐的约定式提交工作流，自动管理版本和 CHANGELOG。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 和 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)：用于增强 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可选用户界面。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想让你的项目出现在上面吗？_[提交 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

41
content/v1.0.0/index.de.md
View File

@ -171,44 +171,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## Über
Die Spezifikation für konventionelle Commits ist von den [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) inspiriert und basiert stark auf diesen.
Der erste Entwurf dieser Spezifikation wurde in Zusammenarbeit mit einigen der folgenden Personen verfasst:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): Eine Reihe von Tools zum Parsen konventioneller Commits aus Git-Protokollen.
* [bumped](https://bumped.github.io): Ein Tool zum Freigeben von Software, mit dem Aktionen vor und nach dem Freigeben einer neuen Version Ihrer Software einfach ausgeführt werden können.
* [unleash](https://github.com/netflix/unleash): Ein Tool zur Automatisierung der Softwareversion und des Veröffentlichungslebenszyklus.
* [lerna](https://github.com/lerna/lerna): ein Tool zur Verwaltung von Monorepos, das aus dem Babel-Projekt hervorgegangen ist.
## Werkzeuge für konventionelle Commits
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): folgt der Spezifikation, um Versionen zu verwalten und automatisch ein Changelog zu generieren
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Ein Tool, das entwickelt wurde, um Commit-Nachrichten gemäß den konventionellen Commit-Spezifikationen zu erstellen.
Konfigurierbar und verwendbar für PHP-Projekte als Composer-Abhängigkeit oder global für Nicht-PHP-Projekte
* [conform](https://github.com/autonomy/conform): Ein Tool, mit dem Richtlinien für Git-Repositories, einschließlich konventioneller Commits, durchgesetzt werden können.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatische Versionierung und CHANGELOG-Verwaltung mit der neuen Squash-Schaltfläche von GitHub und dem empfohlenen Workflow für konventionelle Commits.
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Unterstützung für _konventionelle Commits_ für [JetBrains-Editoren](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): In Go geschriebenes Tool, um zu überprüfen, ob die Commits für einen Branch konventionellen Commits entsprechen. Kommt mit Docker-Image für CI-Anwendungen.
* [semantic-release](https://github.com/semantic-release/semantic-release): Ein Tool, das den gesamten Workflow für die Paketfreigabe automatisiert, einschließlich: Ermitteln der nächsten Versionsnummer, Generieren der Versionshinweise und Veröffentlichen des Pakets.
## Projekte, die konventionelle Commits benutzen
* [yargs](https://github.com/yargs/yargs): Der allseits beliebte Piraten-Parser für Befehlszeilenargumente.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): eine Sammlung von Open-Source-Tools und -Bibliotheken, mit denen Sie Ihren JavaScript-Tests Testabdeckung hinzufügen können.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) und [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optionale zusätzliche Benutzeroberfläche zur Verbesserung von [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Eine Datenzugriffsbibliothek für Node und PostgreSQL.
* [electron](https://github.com/electron/electron): Erstellen Sie plattformübergreifende Desktop-Apps mit JavaScript, HTML und CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Ein einfach zu verwendendes Scroll-Utility-Paket zum Zentrieren von Elementen und für flüssige Animationen.
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-freies Open Source UI-Toolkit.
* [Monica](https://github.com/monicahq/monica): Ein Open Source Personal Relationship Management System.
* [mhy](https://mhy.js.org): Eine konfigurationsfreie, sofort einsatzbereite, Mehrzweck-Toolbox und Entwicklungsumgebung.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo mit ~100 TypeScript-Projekten für die datengetriebene Entwicklung.
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 Eine verbesserte Yii2-App-Vorlage.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Vorlage zur einfachen und schnellen Erstellung Ihres Online-Lebenslaufs.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_Möchten Sie Ihr Projekt auf dieser Liste haben?_ [Senden Sie einen Pull Request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

44
content/v1.0.0/index.fr.md
View File

@ -180,47 +180,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## A Propos
La spécification Conventional Commits s’inspire largement de [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
La première version de cette spécification a été écrite en collaboration avec certaines personnes contribuant à:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): Un ensemble d'outils permettant d'analyser les messages des commits classiques à partir des historiques git.
* [bumped](https://bumped.github.io): Un outil de publication de logiciel qui facilite l'exécution d'actions avant et après la publication d'une nouvelle version de votre logiciel.
* [unleash](https://github.com/netflix/unleash): Un outil pour automatiser le versioning d'un logiciel et du cycle de publication.
* [lerna](https://github.com/lerna/lerna): Un outil de gestion de monorepos, qui a grandi du projet Babel.
## Outils pour Conventional Commits
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): suit la spécification pour gérer les versions et générer automatiquement un journal des modifications.
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Un outil conçu pour créer des messages de commit en suivant les spécifications de Conventional Commits.
Configurable et utilisable pour les projets PHP en tant que dépendance composer ou utilisable globalement pour les projets non-PHP.
* [conform](https://github.com/autonomy/conform): Un outil qui peut être utilisé pour appliquer des stratégies sur les référentiels git, y compris les commits classiques.
* [standard-version](https://github.com/conventional-changelog/standard-version): Le versioning automatique et la gestion de CHANGELOG, en utilisant le nouveau bouton squash de GitHub et le flux de travail Conventional Commits est recommandé.
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Ajoute le support de _Conventional Commits_ pour [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): Outil pour Go pour vérifier si les commits sur la branche sont conformes à Conventional Commits. Livré avec l'image Docker pour les utilisations de CI.
* [semantic-release](https://github.com/semantic-release/semantic-release): Un outil qui automatise l'intégralité du workflow de publication du package, notamment: déterminer le numéro de version suivant, générer les notes de publication et publier le package.
* [Turbogit](https://b4nst.github.io/turbogit) Un outils en ligne de commande pour vous aider a respecter _Conventional Commits_.
## Projets Utilisant Conventional Commits
* [yargs](https://github.com/yargs/yargs): Le parseur d'arguments en ligne de commande sur le thème des pirates préféré de tous.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): une collection d'outils et de bibliothèques open source permettant d'ajouter une couverture de test à vos tests JavaScript.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) et [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Amélioration optionnelle de l'interface utilisateur [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Une bibliothèque d'accès aux données pour Node et PostgreSQL.
* [electron](https://github.com/electron/electron): Créez des applications de bureau multiplates-formes avec JavaScript, HTML et CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un utilitaire de défilement simple à utiliser pour le centrage des éléments et des animations fluides
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework gratuit d'interface utilisateur open source.
* [Monica](https://github.com/monicahq/monica): Un système de gestion de relations personnelles open source.
* [mhy](https://mhy.js.org): 🧩 Une boîte à outils et un environnement de développement multifonctions zéro-config, prêts à l'emploi.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo de ~100 projets TypeScript pour le développement piloté par les données
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 Un modèle d'application Yii2 amélioré.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Un modèle pour créer facilement et rapidement son CV en ligne.
* [Formulaires Nintex](https://www.nintex.fr/plateforme-de-processus/#forms): Créez facilement des formulaires en ligne dynamiques pour capturer et soumettre des données précises et actuelles.
* [Tina CMS](https://tinacms.org): Une boîte à outil open source pour permettre la gestion de contenu côté client sur votre site web.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_envie d'avoir votre projet sur cette liste ?_ [envoyer une pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

45
content/v1.0.0/index.id.md
View File

@ -174,48 +174,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## Tentang
Spesifikasi Conventional Commit terinspirasi oleh, dan didasarkan pada, [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
Draf pertama spesifikasi ini telah ditulis bersama dengan beberapa orang yang berkontribusi pada:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): seperangkat alat untuk mem-parsing pesan komit konvensional dari riwayat git.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Utilitas penguraian yang sesuai dengan spesifikasi untuk mendapatkan objek seperti `{ header: { type, scopre, subject }, body, footer }` dari string pesan komit yang diberikan.
* [bumped](https://bumped.github.io): alat untuk merilis perangkat lunak yang memudahkan untuk melakukan tindakan sebelum dan sesudah merilis versi baru perangkat lunak Anda.
* [unleash](https://github.com/netflix/unleash): alat untuk mengotomatiskan rilis perangkat lunak dan siklus penerbitan.
* [lerna](https://github.com/lerna/lerna): alat untuk mengelola monorepos, yang tumbuh dari proyek Babel.
## Alat untuk Komit Konvensional
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): mengikuti spesifikasi untuk mengelola versi dan menghasilkan changelog secara otomatis.
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen):
alat yang dibuat untuk membuat pesan komit mengikuti spesifikasi Komitmen Konvensional.
Dapat dikonfigurasi dan digunakan untuk proyek PHP sebagai dependensi komposer atau dapat digunakan secara global untuk proyek non-PHP.
* [conform](https://github.com/autonomy/conform): alat yang dapat digunakan untuk menerapkan repositori, termasuk conventional commits.
* [standard-version](https://github.com/conventional-changelog/standard-version): Versi otomatis dan manajemen CHANGELOG, menggunakan tombol squash baru GitHub dan alur kerja Conventional Commits yang direkomendasikan.
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Menambahkan _Conventional Commits_ support untuk [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): Alat go (golang) untuk pengecekan jika komit dalam branch patuh pada conventional commit. Dilengkapi dengan docker image untuk kebutuhan CI.
* [semantic-release](https://github.com/semantic-release/semantic-release): Alat yang mengotomatiskan seluruh alur kerja rilis paket termasuk: menentukan nomor versi berikutnya, menghasilkan catatan rilis dan menerbitkan paket.
## Proyek Menggunakan Conventional Commits
* [yargs](https://github.com/yargs/yargs): parser argumen baris perintah bertema bajak laut favorit semua orang.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): koleksi alat dan pustaka sumber terbuka untuk menambahkan cakupan tes ke tes JavaScript Anda.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) dan [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Opsi peningkatan antarmuka pengguna tambahan [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): Pustaka akses data untuk Node dan PostgreSQL.
* [electron](https://github.com/electron/electron): Bangun aplikasi desktop lintas platform dengan JavaScript, HTML, dan CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Paket utilitas gulir yang mudah digunakan untuk elemen pemusatan, dan animasi yang halus
* [Blaze UI](https://github.com/BlazeUI/blaze): Kerangka kerja perangkat UI sumber bebas terbuka.
* [Monica](https://github.com/monicahq/monica): Sumber Terbuka sistem manajemen hubungan pribadi.
* [mhy](https://mhy.js.org): 🧩 Toolbox nol-konfigurasi, out-of-the-box, multiguna dan lingkungan pengembangan.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo dari ~100 proyek TypeScript untuk pengembangan berbasis data
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 Templat aplikasi Yii2 yang disempurnakan.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Templat untuk membuat CV online Anda dengan mudah dan cepat.
* [Belajarpython](https://github.com/belajarpythoncom/belajarpython.com) Situs Open Source Tutorial Pemrograman Python.
* [Formulir Nintex](https://www.nintex.com/workflow-automation/modern-forms/): Membuat formulir online dinamis dengan mudah untuk menangkap dan mengirimkan data yang akurat dan terkini.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_ingin proyek Anda ada dalam daftar ini?_ [kirimkan pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

37
content/v1.0.0/index.it.md
View File

@ -168,40 +168,3 @@ Non è la fine del mondo se un commit non segue la specifica Commit Convenzional
### Devono tutti i contributori seguire la specifica Commit Convenzionali?
No. Se usi un workflow basato sugli squash di Git, i mantenitori possono pulire i messaggi dei commit mentre vengono inseriti nel branch principale (merge), non aggiungendo alcun carico di lavoro ai committer occasionali. Un workflow comune è quello di unire (con lo squash) automaticamente i commit dalle pull request e far utilizzare un form ai mantenitori per riscrivere un messaggio più adeguato.
## A proposito
La specifica Commit Convenzionali è ispirata e fortemente basata su [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
La prima bozza di questa specifica è stata scritta in collaborazione con alcuni contributori di:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): un set di tool per analizzare messagi dei commit convenzionali dalla cronologia git.
* [parse-commit-message](https://npmjs.com/package/parse-commit-message): Funzionalità per interagire e validare i messaggi che seguono Commit Convenzionali.
* [bumped](https://bumped.github.io): un tool per il rilascio di software il quale rende più semplice eseguire azioni prima o dopo il rilascio di una versione del vostro software.
* [unleash](https://github.com/netflix/unleash): un tool per automatizzare rilasci e cicli di pubblicazioni di un software.
* [lerna](https://github.com/lerna/lerna): un tool per la gestione di monorepos, nato del progetto Babel.
## Strumenti per Conventional Commits
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): un tool realizzato per creare dei messaggi che si basano sulla specifica Conventional Commits.
Totalmente configurabile ed eè utilizzabile per progetti PHP installandola come dipendenza locale o globale per progetti non basati su PHP.
* [conform](https://github.com/autonomy/conform): un tool che può essere usato per introdurre regole sui repository basasti su git, includendo conventional commits.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatizza il versionamento e la gestione del CHANGELOG utilizzando il nuovo pulsante squash di GitHub e il flusso di lavoro consigliato da Commit Convenzionali.
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): offre completamento estensibile basato sul contesto o su template, ed ispezioni, per Conventional Commits all'interno del dialogo di commit per il VCS configurato. Disponibile per tutti gli [IDE JetBrains](https://www.jetbrains.com/).
## Progetti che usano Commit Convenzionali
* [yargs](https://github.com/yargs/yargs): Parser di argomenti da CLI, a tema pirati.
* [parse-commit-message](https://github.com/olstenlarck/parse-commit-message): Tool per analizzare i messaggi dei commit e creare oggetti simili a `{ header: { type, scope, subject }, body, footer }`.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): Una collezione di strumenti e librerie open source per aggiungere la coverage dei test JavaScript.
* [massive.js](https://github.com/dmfay/massive-js): un DBAL per Node e PostgreSQL.
* [electron](https://github.com/electron/electron): Realizza app desktop cross platform utilizzando JavaScript, HTML e CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Un package dal semplice utilizzo per centrare elementi e animazioni fluide.
* [Blaze UI](https://github.com/BlazeUI/blaze): Set di tool open source per UI.
* [Monica](https://github.com/monicahq/monica): Una piattaforma open source per gestire relazioni.
* [mhy](https://mhy.js.org): 🧩 Un set di tool per l'ambiente di sviluppo senza configurazione.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_vuoi aggingere il tuo progetto alla lista?_ [invia una pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

42
content/v1.0.0/index.ja.md
View File

@ -203,45 +203,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## 要約
Conventional Commits の仕様は [Angular Commit Guidlines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) に触発されており、これに大きく基づいています。
この仕様書の最初のドラフトは、何人かの以下のツールのコントリビューターたちとの協力によって書かれました:
* [traditional-changelog](https://github.com/conventional-changelog/conventional-changelog): git 履歴から Conventional Commits のメッセージを解析するツールのセット。
* [bumped](https://bumped.github.io): ソフトウェアの新しいバージョンをリリースする前後にアクションを実行することを手助けするためのツール。
* [unleash](https://github.com/netflix/unleash): ソフトウェアのリリースを自動化し、ライフサイクルを公開するためのツール。
* [lerna](https://github.com/lerna/lerna): Babel プロジェクトから生まれたモノレポを管理するためのツール。
## Conventional Commits のためのツール一覧
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): 仕様に従ってバージョンを管理し、更新ログを自動的生成します。
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Conventional Commits の仕様に従ってコミットメッセージを作成するためのツール。
composer に依存する PHP プロジェクトに対して設定、使用可能であり、非 PHP プロジェクトに対してもグローバルに使用可能。
* [conform](https://github.com/autonomy/conform): Conventional Commits を含めた git リポジトリにポリシーを強制するために使用できるツール。
* [standard-version](https://github.com/conventional-changelog/standard-version): GitHub の新しい squash ボタンと推奨されている Conventional Commits ワークフローを使用した、自動のバージョン管理と CHANGELOG 管理。
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): [JetBrains Editors](https://www.jetbrains.com/)にConventional Commitsサポートを追加します。(IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): ブランチのコミットが Conventional Commits に準拠しているかどうかを確認するための Go 言語で書かれたツール。CI 用の Docker イメージがあります。
* [semantic-release](https://github.com/semantic-release/semantic-release): 次のバージョン番号の決定、リリースノートの生成、パッケージの公開など、パッケージリリースのワークフロー全体を自動化するツール。
## Conventional Commits を利用しているプロジェクト
* [yargs](https://github.com/yargs/yargs): 多くの人に人気な海賊をテーマにしたコマンドライン引数パーサ。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): JavaScript のテストにテストのカバレッジを追加するためのオープンソースのツールとライブラリのコレクション。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) と [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): 追加の [Apereo uPortal](https://www.apereo.org/projects/uportal) でユーザーインターフェースを強化できます。
* [massive.js](https://github.com/dmfay/massive-js): Node と PostgreSQL 用のデータアクセスライブラリ。
* [electron](https://github.com/electron/electron): JavaScript、HTML および CSS を使用してクロスプラットフォームのデスクトップアプリケーションを構築します。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): 要素のセンタリング、スムーズなスクロールアニメーションを簡単に実現するためのスクロールユーティリティパッケージです。
* [Blaze UI](https://github.com/BlazeUI/blaze): フレームワークに依存しないオープンソース UI ツールキット。
* [Monica](https://github.com/monicahq/monica): オープンソースの人的関係管理システム。
* [mhy](https://mhy.js.org): 🧩 設定不要ですぐに使える多目的ツールボックスおよび開発環境。
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): ~100 個ほどのデータ駆動型開発用の TypeScript プロジェクトを集めたのモノレポ。
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 強化された Yii2 アプリテンプレート。
* [dcyou/resume](https://github.com/dcyou/resume): 😎 オンライン履歴書を素早く簡単に作成できるテンプレート。
* [Nintex fōmuzu](https://www.nintex.jp/process-platform/#forms): 動的なオンラインフォームを簡単に作成して、正確で最新のデータをキャプチャして送信します。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_あなたのプロジェクトをこのリストに載せたいですか？_ [プルリクエストを送ってください](https://github.com/conventional-changelog/conventionalcommits.org/pulls)。

42
content/v1.0.0/index.ko.md
View File

@ -168,45 +168,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## About
Conventional Commits 규격은 [앵귤러 커밋 가이드라인](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)에서 영감을 받았으며 이를 토대로 하고 있습니다.
이 규격의 첫 번째 초안은 아래 언급된 프로젝트에 기여하고 있는 분들과의 협업으로 작성되었습니다:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): Git 히스토리에서 conventional commit 메시지를 구문 분석하기 위한 도구 모음.
* [bumped](https://bumped.github.io): 소프트웨어의 새 버전을 릴리즈하기 전후에 작업을 쉽게 수행할 수 있는 소프트웨어를 릴리즈하기 위한 도구.
* [unleash](https://github.com/netflix/unleash): 소프트웨어 릴리즈 및 배포 수명 주기를 자동화하기 위한 도구.
* [lerna](https://github.com/lerna/lerna): Babel 프로젝트에서 성장한 monorepo를 관리하기 도구.
## Conventional Commits를 위한 도구
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): 규격에 따라 버전을 관리하고 changelog를 자동으로 만드는 도구.
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Conventional Commits 규격에 따라 커밋 메시지를 생성하기 위해 사용되는 도구로 PHP 프로젝트에서 컴포저 의존성으로 구성 및 사용할 수 있거나 PHP 이외의 프로젝트에서 전 세계적으로 사용할 수 있습니다.
* [conform](https://github.com/autonomy/conform): Conventional Commits를 포함한 git 저장소에서 정책을 강제하는데 사용되는 도구.
* [standard-version](https://github.com/conventional-changelog/standard-version): GitHub의 스쿼시 버튼과 Conventional Commits 워크플로우를 이용한 자동 버전 지정 및 CHANGELOG 관리.
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): [JetBrains 편집기](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...)에 _Conventional Commits_ 지원 추가.
* [commitsar](https://github.com/commitsar-app/commitsar): 브랜치의 커밋이 Conventional Commit을 지켰는지 검사하는 Go 언어 도구. CI 용으로 Docker 이미지도 제공.
* [semantic-release](https://github.com/semantic-release/semantic-release): 패키지 배포 워크플로우를 자동화해주는 툴. 다음 버전 번호 결정, 릴리즈 노트 생성, 패키지 배포 등의 자동화된 기능 포함.
## Conventional Commits를 이용하고 있는 프로젝트
* [yargs](https://github.com/yargs/yargs): 모두가 가장 좋아하는 해적 테마의 커맨드 라인 인자 구문 분석기.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): 자바스크립트 테스트에 테스트 적용 범위를 추가하는 오픈 소스 도구 및 라이브러리 모음.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal)와 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): [Apereo uPortal](https://www.apereo.org/projects/uportal)을 향상시켜주는 옵션으로 추가 가능한 사용자 인터페이스.
* [massive.js](https://github.com/dmfay/massive-js): Node와 PostgreSQL을 위한 데이터 접근 라이브러리
* [electron](https://github.com/electron/electron): 자바스크립트, HTML, 그리고 CSS를 이용하여 크로스 클랫폼 데스크탑 앱을 만드는 프레임워크.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): 사용하기 쉬운, 요소 중앙 정렬 및 부드러운 애니메이션을 위한 스크롤 유틸리티 패키지.
* [Blaze UI](https://github.com/BlazeUI/blaze): 프레임워크가 필요 없는 오픈소스 UI 툴킷.
* [Monica](https://github.com/monicahq/monica): 오픈 소스 개인 관계 관리 시스템.
* [mhy](https://mhy.js.org): 설정이 필요 없고 바로 사용 가능한 다목적 툴 박스와 개발 환경
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): 데이터 중심 개발을 위한 ~100개의 TypeScript 프로젝트 monorepo
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 향상된 Yii2 앱 템플릿.
* [dcyou/resume](https://github.com/dcyou/resume): 쉽고 빠르게 온라인 이력서를 만들어주는 템플릿.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): 정확하고 최신의 데이터를 수집하기 위한 쉬운 동적 온라인 설문 생성기.
* [Tina CMS](https://tinacms.org): CMS 프론트엔드를 만들어주는 오픈 소스 툴킷.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_위의 목록에 여러분의 프로젝트를 남기고 싶으세요??_ [PR을 만들어보세요](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

79
content/v1.0.0/index.md
View File

@ -186,81 +186,4 @@ One recommendation is to use the `revert` type, and a footer that references the
revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## About
The Conventional Commits specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
The first draft of this specification has been written in collaboration with some of the folks contributing to:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a set of tools for parsing Conventional Commits messages from git histories.
* [parse-commit-message](https://npmjs.com/package/parse-commit-message): Extensible utilities for parsing, stringify and validating Conventional Commit messages.
* [bumped](https://bumped.github.io): a tool for releasing software that makes it easy to perform actions before and after releasing a new version of your software.
* [unleash](https://github.com/netflix/unleash): a tool for automating the software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out of the Babel project.
## Tooling for Conventional Commits
* [go-conventionalcommits](https://github.com/leodido/go-conventionalcommits): Full Go powers to parse conventional commits
* [go-conventional-commit](https://gitlab.com/digitalxero/go-conventional-commit14): go library for parsing commit messages following the specification.
* [chglog](https://github.com/goreleaser/chglog): a tool for parsing Conventional Commits messages from git histories and turning them into templateable change logs.
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): follows the specification to manage versions and generate a changelog automatically
* [commitizen/cz-cli](https://github.com/commitizen/cz-cli): A Node.js tool to create commit messages following the Conventional Commits specs.
* [commitizen-tools/commitizen](https://github.com/commitizen-tools/commitizen): A tool written in Python to create commiting rules for projects, auto bump versions and auto changelog generation.
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): A PHP tool built to create commit messages following the Conventional Commits specs.
Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [php-conventional-changelog](https://github.com/marcocesarato/php-conventional-changelog): a tool built to generate a changelog from a project's committing history messages and metadata and automate versioning with Semver, following Conventional Commits specs. Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [commitlint](https://github.com/conventional-changelog/commitlint): A linter to check that your commit messages meet the Conventional Commits format.
* [gitlint](https://github.com/jorisroovers/gitlint): Git commit message linter written in Python, which can be configured to [enforce Conventional Commits format](https://jorisroovers.com/gitlint/contrib_rules/#ct1-contrib-title-conventional-commits).
* [conform](https://github.com/autonomy/conform): a tool that can be used to enforce policies on git repositories, including Conventional Commits.
* [detect-next-version](https://npmjs.com/package/detect-next-version): Parse, detect and get more metadata about given Conventional Commits.
* [recommended-bump](https://www.npmjs.com/package/recommended-bump): Calculcates the recommended version bump based on given Conventional Commits.
* [git-commits-since](https://www.npmjs.com/package/git-commits-since): Get all (raw) commits since period or (by default) from latest git SemVer tag, plus plugins support.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): provides extensible context and template-based completion, and inspections, for Conventional Commits inside the VCS Commit dialog. Available for all [JetBrains IDEs](https://www.jetbrains.com/).
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Add Conventional Commits support to [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are Conventional Commits compliant. Comes with Docker image for CI uses.
* [semantic-release](https://github.com/semantic-release/semantic-release): A tool that automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package.
* [python-semantic-release](https://github.com/relekang/python-semantic-release): Automatic Semantic Versioning for Python projects. This is a Python implementation of the [semantic-release](https://github.com/semantic-release/semantic-release) for Node.js.
* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): Add Conventional Commits supports for VSCode.
* [Pyhist](https://github.com/jgoodman8/pyhist): A Python utility to automagically update the package version from the git history and generate the Changelog.
* [git-mkver](https://github.com/idc101/git-mkver): A tool to automatically apply Semantic Versioning to git repositories based on _Conventional Commits_.
* [Conventional Commits Next Version](https://gitlab.com/DeveloperC/conventional_commits_next_version): A tooling and language agnostic utility to calculate the next semantic version based on the _Conventional Commits_ since the prior version. Supports monorepos.
* [change](https://github.com/adamtabrams/change): A tool for generating and updating a changelog using Conventional Commits.
* [Turbogit](https://b4nst.github.io/turbogit): A command line tool to help you follow _Conventional Commits_ flow.
* [sv4git](https://github.com/bvieira/sv4git): A command line tool (CLI) to validate commit messages, bump versions, create tags and generate changelogs.
* [Versio](https://github.com/chaaz/versio): A monorepo-compatible tool that updates version numbers based on conventional commits and project dependencies. It can generate tags and changelogs, too.
* [Git Changelog Lib](https://github.com/tomasbjerre/git-changelog-lib): A Java library that supports rendering a changelog given a context derived from Git. Supports conventional commits with [Handlebars Helpers](https://github.com/tomasbjerre/git-changelog-lib#helpers). It is used in:
* [Gradle](https://github.com/tomasbjerre/git-changelog-gradle-plugin)
* [Maven](https://github.com/tomasbjerre/git-changelog-maven-plugin)
* [Jenkins](https://github.com/jenkinsci/git-changelog-plugin)
* [Command Line](https://github.com/tomasbjerre/git-changelog-command-line)
## Projects Using Conventional Commits
* [NFPM](https://github.com/goreleaser/nfpm): NFPM is Not FPM - a simple deb, rpm and apk packager written in Go
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools and libraries for adding test coverage to your JavaScript tests.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) and [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optional supplemental user interface enhancing [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): A data access library for Node and PostgreSQL.
* [electron](https://github.com/electron/electron): Build cross-platform desktop apps with JavaScript, HTML, and CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): A simple to use scroll utility package for centering elements, and smooth animations
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free open source UI toolkit.
* [Monica](https://github.com/monicahq/monica): An open source personal relationship management system.
* [mhy](https://mhy.js.org): A zero-config, out-of-the-box, multi-purpose toolbox and development environment.
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): Simple parser for Diff files (unified diff format).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): Easy split of .diff & .patch into its files.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo of ~100 TypeScript projects for data driven development
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 An enhanced Yii2 app template.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Template to easily and quickly create your online CV.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
* [Tina CMS](https://tinacms.org): An open source toolkit for building front-end content-management into your website.
* [Belajarpython](https://github.com/belajarpythoncom/belajarpython.com) Open source Indonesian python programming tutorial site.
* [Uno Platform](https://platform.uno): Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
* [Jenkins X](https://jenkins-x.io/): Jenkins X provides pipeline automation, built-in GitOps, and preview environments to help teams collaborate and accelerate their software delivery at any scale.
* [Changeloguru](https://github.com/haunt98/changeloguru): Auto-generate changelog from conventional commits, written in Go.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_want your project on this list?_ [send a pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).
```

62
content/v1.0.0/index.pt-br.md
View File

@ -174,65 +174,3 @@ revert: nunca mais falaremos do incidente do miojo
Refs: 676104e, a215868
```
## Sobre
A especificação do Conventional Commits é inspirada e fortemente baseada na [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
O primeiro rascunho desta especificação foi escrito em colaboração com algumas pessoas que contribuem para:
- [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): um conjunto de ferramentas para analisar mensagens de commit baseados no Conventional Commit a partir do histórico git.
- [parse-commit-message](https://npmjs.com/package/parse-commit-message): Utilitários extensíveis para analisar, transformar e validar mensagens de commit baseados no Conventional Commit.
- [bumped](https://bumped.github.io): uma ferramenta que facilita o "release" de software. Facilitando executar ações antes e depois de uma liberar uma nova versão.
- [unleash](https://github.com/netflix/unleash): uma ferramenta para automatizar o ciclo de "release" e publicação de software.
- [lerna](https://github.com/lerna/lerna): uma ferramenta para gerenciar monorepos, que surgiu do projeto Babel.
## Ferramentas para Conventional Commits
- [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): segue a especificação para gerenciar versões e gerar um changelog automaticamente.
- [commitizen/cz-cli](https://github.com/commitizen/cz-cli): Uma ferramenta Node.js para criar mensagens de confirmação seguindo as especificações do Conventional Commits.
- [commitizen-tools/commitizen](https://github.com/commitizen-tools/commitizen): Uma ferramenta escrita em Python para criar regras de confirmação para projetos, versões auto bump e geração automática de changelog.
- [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): Uma ferramenta PHP construída para criar mensagens de confirmação seguindo as especificações do Conventional Commits.
Configurável e utilizável em projetos PHP como uma dependência composer ou utilizável globalmente para projetos que não usam a linguagem PHP.
- [commitlint](https://github.com/conventional-changelog/commitlint): Um linter para verificar se suas mensagens de confirmação atendem ao formato do Conventional Commits.
- [gitlint](https://github.com/jorisroovers/gitlint): Linter de mensagem Git commit escrito em Python, que pode ser configurado para aplicar o formato do Conventional Commits.
- [conform](https://github.com/autonomy/conform): uma ferramenta que pode ser usada para impor políticas em repositórios git, incluindo Conventional Commits.
- [detect-next-version](https://npmjs.com/package/detect-next-version): Analise, detecte e obtenha mais metadados de mensagens de commit do Conventional Commits.
- [recommended-bump](https://www.npmjs.com/package/recommended-bump): Calcula o aumento da versão recomendada com base nas mensagens de commit do Conventional Commits.
- [git-commits-since](https://www.npmjs.com/package/git-commits-since): Obtenha todos os commits (crus) desde o período ou (por padrão) da última tag git SemVer, além de suporte a plug-ins.
- [standard-version](https://github.com/conventional-changelog/standard-version): Geração automática de versões e gerenciamento de CHANGELOG, usando o novo botão de squash do GitHub e o workflow recomendado do Conventional Commits.
- [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): fornece contexto extensível e conclusão baseada em modelo e inspeções para o Conventional Commits dentro da caixa de diálogo Confirmação VCS. Disponível para todos os [IDEs JetBrains](https://www.jetbrains.com/).
- [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Adicione o suporte ao Conventional Commits para [Editores JetBrains](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
- [commitsar](https://github.com/commitsar-app/commitsar): Ferramenta Go para verificar se os commits no branch são compatíveis com o Conventional Commits. Vem com imagem Docker para uso de CI.
- [semantic-release](https://github.com/semantic-release/semantic-release): Uma ferramenta que automatiza todo o fluxo de trabalho de lançamento do pacote, incluindo: determinar o próximo número da versão, gerar as notas de lançamento e publicar o pacote.
- [python-semantic-release](https://github.com/relekang/python-semantic-release): Controle de versão semântico automático para projetos Python. Esta é uma implementação Python do [semantic-release](https://github.com/semantic-release/semantic-release) para Node.js.
- [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): Adiciona suporte para Conventional Commits ao VSCode.
- [Pyhist](https://github.com/jgoodman8/pyhist): Um utilitário Python para atualizar automaticamente a versão do pacote do histórico do git e gerar o Changelog.
- [git-mkver](https://github.com/idc101/git-mkver): Uma ferramenta para aplicar automaticamente semantic-version aos repositórios git com base no Conventional Commits.
- [Conventional Commits Next Version](https://gitlab.com/DeveloperC/conventional_commits_next_version): Um utilitário agnóstico de ferramenta/linguagem para calcular o próximo semantic-release com base nas mensagens de confirmação Git do Conventional Commits desde a última versão.
- [sv4git](https://github.com/bvieira/sv4git): Um CLI para ajudar na validação das mensagens de commit (hooks do git), criação de tags, versões e geração de changelogs.
## Projetos Utilizando Conventional Commits
- [yargs](https://github.com/yargs/yargs): o parser de argumentos de linha de comando, com tema de pirata, favorito de todos.
- [istanbuljs](https://github.com/istanbuljs/istanbuljs): uma coleção de ferramentas e bibliotecas de código aberto para adicionar cobertura de teste a seus testes de JavaScript.
- [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) e [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Aperfeiçoamento opcional da interface do usuário [Apereo uPortal](https://www.apereo.org/projects/uportal).
- [massive.js](https://github.com/dmfay/massive-js): Uma biblioteca de acesso a dados para o Node e PostgreSQL.
- [electron](https://github.com/electron/electron): Crie aplicativos desktop cross-platform com JavaScript, HTML e CSS.
- [scroll-utility](https://github.com/LeDDGroup/scroll-utility): Um pacote simples de usar para centralizar elementos e animações suaves.
- [Blaze UI](https://github.com/BlazeUI/blaze): UI Toolkit de código aberto, Framework-free.
- [Monica](https://github.com/monicahq/monica): Um CRM pessoal. Lembre-se de tudo sobre seus amigos e familiares.
- [mhy](https://mhy.js.org): Uma toolbox e sistema para desenvolvimento com zero configuração, pronta para uso, multifuncional.
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): analisador simples para arquivos Diff (formato diff unificado).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): Fácil divisão de .diff e .patch em seus arquivos.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo de aproximadamente 100 projetos TypeScript para desenvolvimento orientado a dados.
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 Um modelo de aplicativo Yii2 aprimorado.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Modelo para criar seu currículo online de forma fácil e rápida.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Crie facilmente formulários online dinâmicos para capturar e enviar dados precisos e atuais.
* [Tina CMS](https://tinacms.org): Um kit de ferramentas de código aberto para criar gerenciamento de conteúdo front-end em seu site.
* [Uno Platform](https://platform.uno): Crie aplicativos para celular, desktop e WebAssembly com C # e XAML. Hoje. Código aberto e com suporte profissional.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_quer seu projeto nesta lista?_ [envie um pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

202
content/v1.0.0/index.ru.md
View File

@ -252,205 +252,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## Об «Соглашении о коммитах»
Спецификация «Соглашения о коммитах» вдохновлена и в значительной степени
основана на [руководстве коммитов Angular][angular-commit-guidelines].
Первый вариант этой спецификации был написан в сотрудничестве с некоторыми
людьми, внёсшими свой вклад в:
* [conventional-changelog][conventional-changelog] — набор инструментов для
анализа сообщений «Соглашения о коммитах» из историй Git.
* [parse-commit-message][parse-commit-message] — расширяемые утилиты для
парсера, преобразования и проверки сообщений «Соглашения о коммитах».
* [bumped][bumped] — инструмент для выпуска программного обеспечения, который
позволяет легко выполнять действия до и после выпуска новой версии вашего
программного обеспечения.
* [unleash][unleash] — инструмент для автоматизации выпуска программного
обеспечения и публикации жизненного цикла.
* [lerna][lerna] — инструмент для управления монорепозиториями, выросший из
проекта Babel.
## Инструменты для «Соглашения о коммитах»
* [go-conventional-commit][go-conventional-commit] — библиотека Go для парсинга
сообщений коммитов в соответствии со спецификацией.
* [chglog][chglog] — инструмент для парсинга сообщений «Соглашения о коммитах»
из историй Git и превращения их в шаблоны списков изменений.
* [fastlane-plugin][fastlane-plugin] — следует спецификации для управления
версиями и автоматического создания списка изменений.
* [commitizen/cz-cli][commitizen/cz-cli] — инструмент Node.js для создания
сообщений коммитов в соответствии со спецификацией «Соглашение о коммитах».
* [commitizen-tools/commitizen][commitizen-tools/commitizen] — инструмент,
написанный на Python, для создания правил коммитов для проектов,
автоматического повышения версий и автоматического создания списка изменений.
* [php-commitizen][php-commitizen] — инструмент PHP, созданный для создания
сообщений коммитов в соответствии со спецификацией «Соглашение о коммитах».
Настраиваемый и может использоваться для проектов PHP по усмотрению автора в
качестве зависимости или использоваться глобально для проектов, отличных от
PHP.
* [commitlint][commitlint] — линтер для проверки соответствия ваших сообщений
коммитов формату «Соглашения о коммитах».
* [gitlint][gitlint] — линтер сообщений коммитов Git, написанный на Python,
который можно настроить для [принудительного применения формата «Соглашения о
коммитах»][enforce-conventional-commits-format].
* [conform][conform] — инструмент, который можно использовать для обеспечения
соблюдения политик в репозиториях Git, включая «Соглашение о коммитах».
* [detect-next-version][detect-next-version] — анализируйте, обнаруживайте и
получайте больше метаданных о заданном «Соглашении о коммитах».
* [recommended-bump][recommended-bump] — вычисляет рекомендуемую версию на
основе заданном «Соглашении о коммитах».
* [git-commits-since][git-commits-since] — получает все (необработанные)
коммиты с периода или (по умолчанию) из последнего тега Git [семантического
версионирования][semver], плюс поддерживает плагины.
* [standard-version][standard-version] — автоматическое управление версиями и
списками изменений с помощью новой кнопки squash в GitHub и рекомендованного
рабочего процесса «Соглашения о коммитах».
* [Conventional Commit][conventional-commit] — предоставляет расширяемый
контекст и завершение на основе шаблонов, а также проверки для «Соглашения о
коммитах» в диалоговом окне коммитов VCS. Доступно для всех [IDE
(интегрированных сред разработки) от JetBrains][jetbrains].
* [Git Commit Template][git-commit-template] — добавьте поддержку «Соглашения о
коммитах» в [редакторы JetBrains][jetbrains] (IntelliJ IDEA, PyCharm,
PhpStorm и т. д.).
* [commitsar][commitsar] — инструмент Go для проверки совместимости коммитов в
ветке с «Соглашением о коммитах». Поставляется с образом Docker для
использования в CI.
* [semantic-release][semantic-release] — инструмент, который автоматизирует
весь рабочий процесс выпуска пакета, включая: определение номера следующей
версии, создание примечаний к выпуску и публикацию пакета.
* [python-semantic-release][python-semantic-release] — автоматическое
семантическое управление версиями для проектов Python. Это реализация
[semantic-release][semantic-release] на Python для Node.js.
* [VSCode Conventional Commits][vscode-conventional-commits] — добавляет
поддержку «Соглашения о коммитах» в VSCode.
* [Pyhist][pyhist] — утилита Python для автоматического обновления версии
пакета из истории Git и создания списка изменений.
* [git-mkver][git-mkver] — инструмент для автоматического применения
семантического управления версиями к репозиториям Git на основе «Соглашения о
коммитах».
* [Conventional Commits Next Version][conventional-commits-next-version] —
инструментальная и языковая независимая утилита для расчёта следующей
семантической версии на основе «Соглашения о коммитах» с учётом предыдущей
версии. Поддерживает монорепозитории.
* [change][change] — инструмент для создания и обновления списка изменений с
помощью «Соглашения о коммитах».
* [Turbogit][turbogit] — инструмент командной строки, который поможет вам
следовать процессу «Соглашения о коммитах».
## Проекты, которые используют «Соглашение о коммитах»
* [NFPM][nfpm] — простой упаковщик deb, rpm и apk, написанный на Go.
* [yargs][yargs] — всеми любимый парсер аргументов командной строки в пиратской
тематике.
* [istanbuljs][istanbuljs] — набор инструментов и библиотек с открытым исходным
кодом для добавления тестового покрытия к вашим тестам JavaScript.
* [uPortal-home][uportal-home] и
[uPortal-application-framework][uportal-application-framework] —
необязательный дополнительный пользовательский интерфейс, улучшающий [Apereo
uPortal][apereo-uportal].
* [massive.js][massive.js] — библиотека доступа к данным для Node.js и
PostgreSQL.
* [electron][electron] — создавайте кроссплатформенные настольные приложения с
помощью JavaScript, HTML и CSS.
* [scroll-utility][scroll-utility] — простой в использовании пакет служебных
программ прокрутки для центрирования элементов и плавной анимации.
* [Blaze UI][blaze-ui] — свободный от фреймворков набор инструментов
пользовательского интерфейса с открытым исходным кодом.
* [Monica][monica] — система управления личными отношениями с открытым исходным
кодом.
* [mhy][mhy] — готовый к использованию универсальный набор инструментов и среда
разработки с нулевой конфигурацией.
* [@tandil/diffparse][@tandil/diffparse] — простой парсер файлов Diff
(унифицированный формат diff).
* [@tandil/diffsplit][@tandil/diffsplit] — простое разделение .diff и .patch на
файлы.
* [@thi.ng/umbrella][@thi.ng/umbrella] — экосистема с широким охватом и
монорепозиторий из 148+ проектов TypeScript для функциональной разработки на
основе данных.
* [yii2-basic-firestarter][yii2-basic-firestarter] — 🔥 улучшенный шаблон
приложения Yii2.
* [dcyou/resume][dcyou/resume] — 😎 шаблон для простого и быстрого создания
онлайн-резюме.
* [Nintex Forms][nintex-forms] — легко создавайте динамические онлайн-формы для
сбора и отправки точных и актуальных данных.
* [Tina CMS][tina-cms] — набор инструментов с открытым исходным кодом для
встраивания интерфейсного управления контентом на ваш веб-сайт.
* [Belajarpython][belajarpython] — индонезийский сайт с открытым исходным кодом
по обучению программирования на Python.
* [Uno Platform][uno-platform] — создавайте мобильные, настольные и WebAssembly
приложения с помощью C# и XAML. Сегодня. Открытый исходный код и
профессиональная поддержка.
* [Jenkins X][jenkins-x] — обеспечивает автоматизацию конвейера, встроенный
GitOps и среды предварительного просмотра, чтобы помочь командам сотрудничать
и ускорить доставку своего программного обеспечения в любом масштабе.
[![Соглашение о коммитах][conventional-commits-img]][conventional-commits]
_Хотите, чтобы ваш проект был в этом списке?_ [Отправьте PR][conventional-commits-pr]!
[semver]: https://semver.org/lang/ru
[@commitlint/config-conventional]: https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional
[angular-convention]: https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines
[git-trailer-format]: https://git-scm.com/docs/git-interpret-trailers
[rfc-2119]: https://www.ietf.org/rfc/rfc2119.txt
[angular-commit-guidelines]: https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines
[conventional-changelog]: https://github.com/conventional-changelog/conventional-changelog
[parse-commit-message]: https://npmjs.com/package/parse-commit-message
[bumped]: https://bumped.github.io
[unleash]: https://github.com/netflix/unleash
[lerna]: https://github.com/lerna/lerna
[go-conventional-commit]: https://gitlab.com/digitalxero/go-conventional-commit14
[chglog]: https://github.com/goreleaser/chglog
[fastlane-plugin]: https://github.com/xotahal/fastlane-plugin-semantic_release
[commitizen/cz-cli]: https://github.com/commitizen/cz-cli
[commitizen-tools/commitizen]: https://github.com/commitizen-tools/commitizen
[php-commitizen]: https://github.com/damianopetrungaro/php-commitizen
[commitlint]: https://github.com/conventional-changelog/commitlint
[gitlint]: https://github.com/jorisroovers/gitlint
[enforce-conventional-commits-format]: https://jorisroovers.com/gitlint/contrib_rules/#ct1-contrib-title-conventional-commits
[conform]: https://github.com/autonomy/conform
[detect-next-version]: https://npmjs.com/package/detect-next-version
[recommended-bump]: https://www.npmjs.com/package/recommended-bump
[git-commits-since]: https://www.npmjs.com/package/git-commits-since
[standard-version]: https://github.com/conventional-changelog/standard-version
[conventional-commit]: https://github.com/lppedd/idea-conventional-commit
[jetbrains]: https://www.jetbrains.com
[git-commit-template]: https://plugins.jetbrains.com/plugin/9861-git-commit-template
[commitsar]: https://github.com/commitsar-app/commitsar
[semantic-release]: https://github.com/semantic-release/semantic-release
[python-semantic-release]: https://github.com/relekang/python-semantic-release
[vscode-conventional-commits]: https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits
[pyhist]: https://github.com/jgoodman8/pyhist
[git-mkver]: https://github.com/idc101/git-mkver
[conventional-commits-next-version]: https://gitlab.com/DeveloperC/conventional_commits_next_version
[change]: https://github.com/adamtabrams/change
[turbogit]: https://b4nst.github.io/turbogit
[nfpm]: https://github.com/goreleaser/nfpm
[yargs]: https://github.com/yargs/yargs
[istanbuljs]: https://github.com/istanbuljs/istanbuljs
[uportal-home]: https://github.com/UW-Madison-DoIT/angularjs-portal
[uportal-application-framework]: https://github.com/UW-Madison-DoIT/uw-frame
[apereo-uportal]: https://www.apereo.org/projects/uportal
[massive.js]: https://gitlab.com/dmfay/massive-js
[electron]: https://github.com/electron/electron
[scroll-utility]: https://github.com/LeDDGroup/scroll-utility
[blaze-ui]: https://github.com/BlazeUI/blaze
[monica]: https://github.com/monicahq/monica
[mhy]: https://mhy.js.org
[@tandil/diffparse]: https://github.com/danielduarte/diffparse#readme
[@tandil/diffsplit]: https://github.com/danielduarte/diffsplit#readme
[@thi.ng/umbrella]: https://github.com/thi-ng/umbrella
[yii2-basic-firestarter]: https://github.com/HunWalk/yii2-basic-firestarter
[dcyou/resume]: https://github.com/dcyou/resume
[nintex-forms]: https://www.nintex.com/workflow-automation/modern-forms
[tina-cms]: https://tinacms.org
[belajarpython]: https://github.com/belajarpythoncom/belajarpython.com
[uno-platform]: https://platform.uno
[jenkins-x]: https://jenkins-x.io
[conventional-commits-img]: https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg
[conventional-commits]: https://conventionalcommits.org/ru
[conventional-commits-pr]: https://github.com/conventional-changelog/conventionalcommit.org/pulls

57
content/v1.0.0/index.th.md
View File

@ -175,60 +175,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## เกี่ยวกับ
ข้อกำหนดของ The Conventional Commits ได้รับแรงบันดาลใจ และอ้างอิงมาจาก [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
แบบร่างฉบับแรกของข้อกำหนดนี้ถูกเขียนขึ้นโดยความร่วมมือของกลุ่มคนที่มีส่วนร่วมในโปรเจกต์เหล่านี้
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): ชุดของเครื่องมือที่จะใช้แยกข้อความ commit ที่สอดคล้องตามข้อตกลงจากประวัติใน git
* [parse-commit-message](https://npmjs.com/package/parse-commit-message): เครื่องมือที่สามารถสร้างส่วนต่อขยายสำหรับในการแยก แปลงให้เป็นข้อความ และตรวจสอบความถูกต้องสำหรับข้อความ commit ที่สอดคล้องตามข้อตกลง
* [bumped](https://bumped.github.io): เครื่องมือที่ใช้ในการรีลีสซอฟต์แวร์ที่ช่วยให้ทำกิจกรรมบางอย่างก่อนและหลังการรีลีสซอฟต์แวร์เวอร์ชั่นใหม่ออกไป
* [unleash](https://github.com/netflix/unleash): เครื่องมือที่จะช่วยในการจัดการวัฏจักรการรีลีสซอฟต์แวร์และเผยแพร่อย่างอัตโนมัติ
* [lerna](https://github.com/lerna/lerna): เครื่องมือในการจัดการซอฟต์แวร์ที่เป็นแบบ monorepo ซึ่งต่อยอดมาจากโปรเจ็กต์ Babel
## เครื่องมือสำหรับ Conventional Commits
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): สอดคล้องกับข้อกำหนดในการจัดการเวอร์ชั่น และสร้างบันทึกการเปลี่ยนแปลงโดยอัตโนมัติ
* [commitizen/cz-cli](https://github.com/commitizen/cz-cli): เครื่องมือสำหรับ Node.js เพื่อใช้สร้างข้อความ commit ที่สอดคล้องตามข้อกำหนดของ Conventional Commits
* [commitizen-tools/commitizen](https://github.com/commitizen-tools/commitizen): เครื่องมือที่เขียนด้วยภาษาไพธอนในการสร้างกฏในการ commit สำหรับโปรเจ็กต์ และช่วยปรับเลขเวอร์ชั่น และสร้างบันทึกการเปลี่ยนแปลงโดยอัตโนมัติ
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): เครื่องมือสำหรับภาษา PHP เพื่อใช้สร้างข้อความ messages ที่สอดคล้องตามข้อกำหนดของ Conventional Commits โดยที่สามารถปรับแต่ง และใช้เป็น depedency ของ composer สำหรับโปรเจ็กต์ PHP หรือใช้โดยทั่วไปสำหรับโปรเจ็กต์ที่ไม่ใช่ PHP
* [commitlint](https://github.com/conventional-changelog/commitlint): ตัวตรวจสอบที่จะตรวจสอบว่าข้อความ commit ของคุณสอดคล้องกับรูปแบบของ Conventional Commits หรือไม่
* [gitlint](https://github.com/jorisroovers/gitlint): ตัวตรวจสอบข้อความ commit สำหรับ git เขียนด้วยภาษาไพธอน สามารถปรับแต่งค่าเพื่อ [บังคับใช้รูปแบบ Conventional Commits](https://jorisroovers.com/gitlint/contrib_rules/#ct1-contrib-title-conventional-commits) ได้
* [conform](https://github.com/autonomy/conform): เครื่องมือที่สามารถบังคับการใช้กฏบน git รวมถึง Conventional Commits ได้
* [detect-next-version](https://npmjs.com/package/detect-next-version): ตัวแยก ตรวจจับ ดึงค่า และดึงลักษณะของ Conventional Commits
* [recommended-bump](https://www.npmjs.com/package/recommended-bump): ช่วยคำนวณเลขเวอร์ชั่นโดยอ้างอิงจาก Conventional Commits
* [git-commits-since](https://www.npmjs.com/package/git-commits-since): ดึงข้อความ commit แบบดิบจากช่วงเวลาหรือจาก tag ใน git ที่อยู่ในรูปแบบ SemVer (โดยปริยาย) และรองรับปลักอิน
* [standard-version](https://github.com/conventional-changelog/standard-version): ช่วยกำหนดเลขเวอร์ชั่นให้โดยอัตโนมัติ และจัดการ CHANGELOG โดยใช้ปุ่มยุบรวม commit (squash) ใหม่ใน GitHub และลำดับการทำงานแบบที่สอดคล้องกับ Conventional Commits
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): จัดเตรียมรูปแบบสำหรับการสร้าง และตรวจสอบ Conventional Commits ที่สามารถเพิ่มเติมได้ภายใต้หน้าจอ ทุกคนสามารถเข้าใช้งานได้ผ่าน [JetBrains IDEs](https://www.jetbrains.com/).
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): เพิ่มการสนับสนุนการใช้ Conventional Commits ในโปรแกรม [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): เครื่องมือสำหรับภาษาโกในการตรวจสอบว่ามี branch ไหนใน git สอดคล้องกับ Conventional Commits หรือไม่ มาพร้อมกับ Docker image สำหรับการใช้งาน CI
* [semantic-release](https://github.com/semantic-release/semantic-release): เครื่องมือที่ช่วยในการจัดการลำดับทั้งหมดในการรีลีสแพ็กเกจแบบอัตโนมัติ รวมไปถึงการกำหนดเลขเวอร์ชั่นถัดไป การสร้างบันทึกในการรีลีส และการปล่อยแพ็คเกจสู่สาธารณะ
* [python-semantic-release](https://github.com/relekang/python-semantic-release): ตัวช่วยกำหนดเลขเวอร์ชั่นแบบ SemVer สำหรับโปรเจกต์ของภาษาไพธอน ส่วนนี่เป็นการพัฒนาด้วยภาษาไพธอนสำหรับ [semantic-release](https://github.com/semantic-release/semantic-release) Node.js
* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): เพิ่มการสนับสนุนการใช้ Conventional Commits ลงใน VSCode
* [Pyhist](https://github.com/jgoodman8/pyhist): เครื่องมือสำหรับภาษาไพธอนในการปรับค่าเวอร์ชั่นจากข้อมูลย้อนหลังใน git และช่วยสร้างบันทึกการเปลี่ยนแปลง
## โปรเจกต์ที่ใช้ Conventional Commits
* [yargs](https://github.com/yargs/yargs): ตัวแยกค่าอากิวเมนต์ผ่าน command line ในแนวไพเรทที่ทุกคนชื่นชอบ
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): ชุดของเครื่องมือและไลบรารี่แบบโอเพ่นซอร์สในการเพิ่ม code coverage ลงไปในชุดทดสอบของจาวาสคริปต์ของคุณ
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) และ [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): ส่วนขยายความสามารถของส่วนติดต่อผู้ใช้เพิ่มเติมของ [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): ไลบรารี่สำหรับเข้าถึงข้อมูลสำหรับ Node และ PostgreSQL
* [electron](https://github.com/electron/electron): สำหรับ Build แอพพลิเคชั่นบนเดสก์ท็อปแบบ cross-platform ด้วยจาวาสคริปต์ HTML และ CSS
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): เครื่องมือที่ช่วยในการเลื่อนหน้าจออย่างง่ายในการทำให้ element อยู่ตรงกลางจอ และมีอนิเมชั่นที่ลื่นไหล
* [Blaze UI](https://github.com/BlazeUI/blaze): เครื่องมือในการจัดการส่วนติดต่อผู้ใช้แบบไม่ได้ใช้เฟรมเวิร์คที่เป็นโอเพ่นซอร์ส
* [Monica](https://github.com/monicahq/monica): ระบบในการจัดการความสัมพันธ์ส่วนบุคคลแบบโอเพ่นซอร์ส
* [mhy](https://mhy.js.org): กล่องเครื่องมือและชุดสภาพแวดล้อมสำหรับการพัฒนาแบบไม่ต้องตั้งค่าอะไร และมีทุกอย่างให้พร้อม และใช้งานได้หลากหลาย
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): ตัวแยกไฟล์ชนิด Diff แบบง่าย (unified diff format).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): ตัวแบ่งไฟล์ .diff และ .patch ออกมาเป็นไฟล์ของใครของมัน
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): ประมาณ 100 โปรเจกต์แบบ monorepo ในภาษา TypeScript สำหรับการพัฒนาแบบ data driven
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 เทมเพลตของแอพพลิเคชั่น Yii2
* [dcyou/resume](https://github.com/dcyou/resume): 😎 เทมเพลตในการสร้าง CV แบบออนไลน์อย่างง่ายและรวดเร็ว
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): สร้างฟอร์มออนไลน์อย่างง่ายและไดนามิกเพื่อรับค่าและส่งข้อมูลที่เป็นปัจจุบันและถูกต้อง
* [Tina CMS](https://tinacms.org): เครื่องมือโอเพ่นซอร์สสำหรับการสร้างตัวจัดการฝั่งหน้าบ้านสำหรับเว็บไซต์ของคุณ
* [Uno Platform](https://platform.uno): สร้างแอพพลิเคชั่นสำหรับมือถือ เดสก์ท็อป และ WebAssembly ด้วยภาษา C# และ XAML วันนี้ โอเพ่นซอร์ส และได้รับการสนับสนุนอย่างมืออาชีพ
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_ต้องการเพิ่มโปรเจกต์ของคุณลงในรายชื่อนี้?_ [ส่ง pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

43
content/v1.0.0/index.tr.md
View File

@ -176,46 +176,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## Hakkında
Conventional Commits şartnamesi, [Angular Commit Kılavuzundan](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) esinlenilmiştir ve buna dayanmaktadır.
Bu şartnamenin ilk taslağı aşağıdakilere katkıda bulunan bazı kişilerle işbirliği içinde yazılmıştır:
- [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog) : git geçmişlerinden gelen Conventional Commits mesajlarını ayrıştırmak için bir dizi araç.
- [bumped](https://bumped.github.io) : Yazılımınızın yeni bir sürümünü yayınlamadan önce ve sonra eylemleri gerçekleştirmeyi kolaylaştıran bir yayınlama aracı.
- [unleash](https://github.com/netflix/unleash) : Yazılım sürümlemenin otomatikleştirilmesi ve yaşam döngüsünün yayınlanması için bir araç.
- [lerna](https://github.com/lerna/lerna) : Babel projesinden çıkıp büyüyen monorepo yönetmek için kullanılan bir araçtır.
## Conventional Commits Araçları
- [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release) : sürümleri yönetmek ve otomatik olarak bir changelog oluşturmak için kabul edilen sözleşmeyi takip eder
- [php-commitizen](https://github.com/damianopetrungaro/php-commitizen) : Conventional Commits sözleşmesini takip eden commit mesajları oluşturmak için oluşturulmuş bir PHP aracı. Composer bağımlılığı olarak PHP projeleri için yapılandırılabilir ve kullanılabilir veya PHP olmayan projeler için global olarak kullanılabilir.
- [conform](https://github.com/autonomy/conform) : Conventional Commits de dahil olmak üzere git repolarında bu tarz politikaları uygulamak için kullanılabilecek bir araç.
- [standart sürüm](https://github.com/conventional-changelog/standard-version) : GitHub'ın yeni squash düğmesini ve önerilen Conventional Commits iş akışını kullanarak otomatik sürüm oluşturma ve CHANGELOG yönetimi.
- [Conventional Commit](https://github.com/lppedd/idea-conventional-commit) : VCS commit iletişim kutusunda Conventional Commits için genişletilebilir bağlam ve şablon tabanlı tamamlama ve denetimler sağlar. Tüm [JetBrains IDE'leri ](https://www.jetbrains.com/) için kullanılabilir.
- [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template) : [JetBrains Editörlerine](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm ...) Conventional Commits desteği ekleyin.
- [commitsar](https://github.com/commitsar-app/commitsar): Yapılan commit'lerin Conventional Commits uyumlu olup olmadığını kontrol etmek için kullanılabilecek Go ile yazılmış bir araç. CI kullanımları için Docker image ile birlikte gelir.
- [semantic-release](https://github.com/semantic-release/semantic-release) : Bir sonraki sürüm numarasının belirlenmesi, sürüm notlarının oluşturulması ve paketin yayınlanması dahil olmak üzere tüm paket sürümü iş akışını otomatikleştiren bir araç.
## Conventional Commits Kullanan Projeler
- [yargs](https://github.com/yargs/yargs) : herkesin en sevdiği korsan temalı komut satırı argüman ayrıştırıcısı.
- [istanbuljs](https://github.com/istanbuljs/istanbuljs) : JavaScript testlerinize test kapsamı eklemek için açık kaynaklı araçlar ve kütüphanelerden oluşan bir koleksiyon.
- [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) ve [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame) : [Apereo uPortal'ı](https://www.apereo.org/projects/uportal) esneklik sağlayan isteğe bağlı tamamlayıcı kullanıcı arabirimi.
- [massive.js](https://github.com/dmfay/massive-js) : Node ve PostgreSQL için bir veri erişim kütüphanesi.
- [electron](https://github.com/electron/electron) : JavaScript, HTML ve CSS ile platform bağımsız masaüstü uygulamaları oluşturun.
- [scroll-utility](https://github.com/LeDDGroup/scroll-utility) : Elemanları ortalamak ve düzgün animasyonlar için kullanımı kolay bir kaydırma yardımcı programı paketi
- [Blaze UI](https://github.com/BlazeUI/blaze) : Çerçeve bağımlılığı olmayan açık kaynak kullanıcı arayüzü araç seti.
- [Monica](https://github.com/monicahq/monica) : Açık kaynaklı bir kişisel ilişki yönetim sistemi.
- [mhy](https://mhy.js.org) : Sıfır yapılandırma, kullanıma hazır, çok amaçlı bir araç kutusu ve geliştirme ortamı.
- [@ thi.ng / umbrella](https://github.com/thi-ng/umbrella) : Veriye dayalı geliştirme için ~100 TypeScript projesinden oluşan bir monorepo
- [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter) : 🔥 Geliştirilmiş bir Yii2 uygulama şablonu.
- [dcyou / resume](https://github.com/dcyou/resume) : 😎 Kolay ve hızlı bir şekilde çevrimiçi CV oluşturmak için şablon.
- [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/) : Doğru ve güncel verileri yakalamak ve göndermek için kolayca dinamik çevrimiçi formlar oluşturun.
- [Tina CMS](https://tinacms.org) : Web sitenize ön uç içerik yönetimi oluşturmak için açık kaynaklı bir araç seti.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)[](https://conventionalcommits.org)[](https://conventionalcommits.org)
*Projenizi bu listede mi istiyorsun?* [PR ile gönderin](https://github.com/conventional-changelog/conventionalcommits.org/pulls) .

77
content/v1.0.0/index.uk.md
View File

@ -170,80 +170,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## Про цей документ
Політика комітів створена в більшості своїй з [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).
Перша чернетка була створена спільними зусиллями нижчевказаних:
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): a set of tools for parsing Conventional Commits messages from git histories.
* [parse-commit-message](https://npmjs.com/package/parse-commit-message): Extensible utilities for parsing, stringify and validating Conventional Commit messages.
* [bumped](https://bumped.github.io): a tool for releasing software that makes it easy to perform actions before and after releasing a new version of your software.
* [unleash](https://github.com/netflix/unleash): a tool for automating the software release and publishing lifecycle.
* [lerna](https://github.com/lerna/lerna): a tool for managing monorepos, which grew out of the Babel project.
## Інструменти для Політики Комітів
* [go-conventionalcommits](https://github.com/leodido/go-conventionalcommits): Full Go powers to parse conventional commits
* [go-conventional-commit](https://gitlab.com/digitalxero/go-conventional-commit14): go library for parsing commit messages following the specification.
* [chglog](https://github.com/goreleaser/chglog): a tool for parsing Conventional Commits messages from git histories and turning them into templateable change logs.
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): follows the specification to manage versions and generate a changelog automatically
* [commitizen/cz-cli](https://github.com/commitizen/cz-cli): A Node.js tool to create commit messages following the Conventional Commits specs.
* [commitizen-tools/commitizen](https://github.com/commitizen-tools/commitizen): A tool written in Python to create commiting rules for projects, auto bump versions and auto changelog generation.
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): A PHP tool built to create commit messages following the Conventional Commits specs.
Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [php-conventional-changelog](https://github.com/marcocesarato/php-conventional-changelog): a tool built to generate a changelog from a project's committing history messages and metadata and automate versioning with Semver, following Conventional Commits specs. Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects.
* [commitlint](https://github.com/conventional-changelog/commitlint): A linter to check that your commit messages meet the Conventional Commits format.
* [gitlint](https://github.com/jorisroovers/gitlint): Git commit message linter written in Python, which can be configured to [enforce Conventional Commits format](https://jorisroovers.com/gitlint/contrib_rules/#ct1-contrib-title-conventional-commits).
* [conform](https://github.com/autonomy/conform): a tool that can be used to enforce policies on git repositories, including Conventional Commits.
* [detect-next-version](https://npmjs.com/package/detect-next-version): Parse, detect and get more metadata about given Conventional Commits.
* [recommended-bump](https://www.npmjs.com/package/recommended-bump): Calculcates the recommended version bump based on given Conventional Commits.
* [git-commits-since](https://www.npmjs.com/package/git-commits-since): Get all (raw) commits since period or (by default) from latest git SemVer tag, plus plugins support.
* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow.
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): provides extensible context and template-based completion, and inspections, for Conventional Commits inside the VCS Commit dialog. Available for all [JetBrains IDEs](https://www.jetbrains.com/).
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Add Conventional Commits support to [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...).
* [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are Conventional Commits compliant. Comes with Docker image for CI uses.
* [semantic-release](https://github.com/semantic-release/semantic-release): A tool that automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package.
* [python-semantic-release](https://github.com/relekang/python-semantic-release): Automatic Semantic Versioning for Python projects. This is a Python implementation of the [semantic-release](https://github.com/semantic-release/semantic-release) for Node.js.
* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): Add Conventional Commits supports for VSCode.
* [Pyhist](https://github.com/jgoodman8/pyhist): A Python utility to automagically update the package version from the git history and generate the Changelog.
* [git-mkver](https://github.com/idc101/git-mkver): A tool to automatically apply Semantic Versioning to git repositories based on _Conventional Commits_.
* [Conventional Commits Next Version](https://gitlab.com/DeveloperC/conventional_commits_next_version): A tooling and language agnostic utility to calculate the next semantic version based on the _Conventional Commits_ since the prior version. Supports monorepos.
* [change](https://github.com/adamtabrams/change): A tool for generating and updating a changelog using Conventional Commits.
* [Turbogit](https://b4nst.github.io/turbogit): A command line tool to help you follow _Conventional Commits_ flow.
* [sv4git](https://github.com/bvieira/sv4git): A command line tool (CLI) to validate commit messages, bump versions, create tags and generate changelogs.
* [Versio](https://github.com/chaaz/versio): A monorepo-compatible tool that updates version numbers based on conventional commits and project dependencies. It can generate tags and changelogs, too.
* [Git Changelog Lib](https://github.com/tomasbjerre/git-changelog-lib): A Java library that supports rendering a changelog given a context derived from Git. Supports conventional commits with [Handlebars Helpers](https://github.com/tomasbjerre/git-changelog-lib#helpers). It is used in:
* [Gradle](https://github.com/tomasbjerre/git-changelog-gradle-plugin)
* [Maven](https://github.com/tomasbjerre/git-changelog-maven-plugin)
* [Jenkins](https://github.com/jenkinsci/git-changelog-plugin)
* [Command Line](https://github.com/tomasbjerre/git-changelog-command-line)
## Проєкти, що використовують Політику Комітів
* [NFPM](https://github.com/goreleaser/nfpm): NFPM is Not FPM - a simple deb, rpm and apk packager written in Go
* [yargs](https://github.com/yargs/yargs): everyone's favorite pirate themed command line argument parser.
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): a collection of open-source tools and libraries for adding test coverage to your JavaScript tests.
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) and [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): Optional supplemental user interface enhancing [Apereo uPortal](https://www.apereo.org/projects/uportal).
* [massive.js](https://github.com/dmfay/massive-js): A data access library for Node and PostgreSQL.
* [electron](https://github.com/electron/electron): Build cross-platform desktop apps with JavaScript, HTML, and CSS.
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): A simple to use scroll utility package for centering elements, and smooth animations
* [Blaze UI](https://github.com/BlazeUI/blaze): Framework-free open source UI toolkit.
* [Monica](https://github.com/monicahq/monica): An open source personal relationship management system.
* [mhy](https://mhy.js.org): A zero-config, out-of-the-box, multi-purpose toolbox and development environment.
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): Simple parser for Diff files (unified diff format).
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): Easy split of .diff & .patch into its files.
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): Monorepo of ~100 TypeScript projects for data driven development
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 An enhanced Yii2 app template.
* [dcyou/resume](https://github.com/dcyou/resume): 😎 Template to easily and quickly create your online CV.
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): Easily create dynamic online forms to capture and submit accurate and current data.
* [Tina CMS](https://tinacms.org): An open source toolkit for building front-end content-management into your website.
* [Belajarpython](https://github.com/belajarpythoncom/belajarpython.com) Open source Indonesian python programming tutorial site.
* [Uno Platform](https://platform.uno): Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
* [Jenkins X](https://jenkins-x.io/): Jenkins X provides pipeline automation, built-in GitOps, and preview environments to help teams collaborate and accelerate their software delivery at any scale.
* [Changeloguru](https://github.com/haunt98/changeloguru): Auto-generate changelog from conventional commits, written in Go.
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_хочете ваш проєкт в списку?_ [надсилайте запит про додавання](https://github.com/conventional-changelog/conventionalcommits.org/pulls).

61
content/v1.0.0/index.zh-hans.md
View File

@ -193,64 +193,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## 关于
约定式提交规范受到了 [Angular 提交准则](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)的启发，并在很大程度上以其为依据。
该规范的首个草案来自下面这些项目中若干贡献者们的协作：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)：一套从 git 历史中解析出约定式提交说明的工具。
* [parse-commit-message](https://npmjs.com/package/parse-commit-message)：用于转换、字符串化、校验约定式提交信息的扩展工具。
* [bumped](https://bumped.github.io)：一个用于发布软件的工具，可以在为你的软件发布新版本前后轻松地执行操作。
* [unleash](https://github.com/netflix/unleash)：一个用于自动化软件发行和发布生命周期的工具。
* [lerna](https://github.com/lerna/lerna)：一个用于管理宏仓库（monorepo）的工具，源自 Babel 项目。
## 用于约定式提交的工具
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): 根据规范管理版本并自动生成变更日志。
* [commitizen/cz-cli](https://github.com/commitizen/cz-cli): Node.js 工具，用于创建遵循约定式提交规范的提交信息。
* [commitizen-tools/commitizen](https://github.com/commitizen-tools/commitizen): Python 编写的项目提交规则创建工具，自动增加版本号并生成变更记录。
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): PHP工具，用于创建遵循约定式提交规范的提交信息。
可配置，并且可以作为 composer 依赖项用于 PHP 项目，或可在非 PHP 项目中全局使用。
* [commitlint](https://github.com/conventional-changelog/commitlint): 用于检查提交信息是否符合约定式提交规范的检查器。
* [gitlint](https://github.com/jorisroovers/gitlint): Python 开发的 Git 提交信息检查器，可以通过 [enforce Conventional Commits format](https://jorisroovers.com/gitlint/contrib_rules/#ct1-contrib-title-conventional-commits) 进行配置。
* [conform](https://github.com/autonomy/conform): 一个可用以在 git 仓库上施加配置的工具，包括约定式提交。
* [detect-next-version](https://npmjs.com/package/detect-next-version): 对约定式提交规范的内容进行解析、检测并提取出元信息。
* [recommended-bump](https://www.npmjs.com/package/recommended-bump): 根据约定式提交的信息计算并推荐新版本号。
* [git-commits-since](https://www.npmjs.com/package/git-commits-since): 获取一个周期内或上一个语义化版本到现在的所有原始提交信息，支持自定义插件。
* [standard-version](https://github.com/conventional-changelog/standard-version): 自动化的版本和 CHANGELOG 管理。使用 GitHub 新的合并提交按钮，并推荐使用约定式提交工作流。
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): 在版本控制系统的提交窗口中提供可扩展的约定式提交规范模板，可以用于所有 [JetBrains IDEs](https://www.jetbrains.com/)。
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): 在 [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...) 中增加约定式提交规范的支持。
* [commitsar](https://github.com/commitsar-app/commitsar): Go 工具，用于检查分支上的提交信息是否符合约定式提交规范，并提供了 Docker 镜像给 CI 用户使用。
* [semantic-release](https://github.com/semantic-release/semantic-release): 一个自动化整个项目的工具，包括：决定下一个版本号，生成发布说明并发布项目包。
* [python-semantic-release](https://github.com/relekang/python-semantic-release): 为 Python 项目提供自动化语义版本。这是一个 Python 版本的 [semantic-release](https://github.com/semantic-release/semantic-release)。
* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): 为 VSCode 添加约定式提交规范的支持。
* [Pyhist](https://github.com/jgoodman8/pyhist): Python 工具，根据 git 历史记录自动更新包版本并生成变更日志。
* [git-mkver](https://github.com/idc101/git-mkver): 根据 _Conventional Commits_ 在 git 项目中自动实现语义化版本的工具。
* [Conventional Commits Next Version](https://gitlab.com/DeveloperC/conventional_commits_next_version): 跨语言工具，从最近的一个版本开始，根据符合 _Conventional Commits_ 的提交信息，计算下一个语义化版本。
## 使用约定式提交的项目
* [yargs](https://github.com/yargs/yargs)：广受欢迎的命令行参数解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs)：一套为 JavaScript 测试生成测试覆盖率的开源工具和类库。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 和 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame)：用于增强 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可选用户界面。
* [massive.js](https://github.com/dmfay/massive-js)：一个用于 Node 和 PostgreSQL 的数据访问类库。
* [electron](https://github.com/electron/electron)：用 JavaScript、HTML 和 CSS 构建跨平台应用。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility)：一个居中元素和平滑动画的滚屏工具包实例。
* [Blaze UI](https://github.com/BlazeUI/blaze)：无框架开源 UI 套件。
* [Monica](https://github.com/monicahq/monica)：一个开源的人际关系管理系统。
* [mhy](https://mhy.js.org)：一个零配置、开箱即用的、多用途工具箱与开发环境。
* [@tandil/diffparse](https://github.com/danielduarte/diffparse#readme): 简单的 Diff 文件解析器（统一 diff 格式）。
* [@tandil/diffsplit](https://github.com/danielduarte/diffsplit#readme): 快速将 .diff 和 .patch 拆分成独立文件。
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): 数据驱动开发的 ~100 个 TypeScript 项目。
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 Yii2应用的增强模板。
* [dcyou/resume](https://github.com/dcyou/resume): 😎 快速创建在线简历的模板。
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): 方便的创建动态在线表单并获准确、实时数据。
* [Tina CMS](https://tinacms.org): 为你的网站创建前端内容管理的开源工具集。
* [Uno Platform](https://platform.uno): 使用 C# 和 XAML 创建移动、桌面和 WebAssembly 应用。今天，开源并给予专业支持。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想让你的项目出现在上面吗？_ [提交 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

47
content/v1.0.0/index.zh-hant.md
View File

@ -185,50 +185,3 @@ revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
```
## 關於
約定式提交規範，是受到 [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) 的啟發，也很大程度以其為依據。
此規範的第一版草稿，是由以下專案的一些貢獻者所協作出來的：
* [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog): 一套用從 git 歷史中解析約定式提交的工具。
* [bumped](https://bumped.github.io): 一個用於發布軟體的工具，讓發布軟體新版本的前後能輕鬆的執行動作。
* [unleash](https://github.com/netflix/unleash): 一個能自動化軟體發布與發行的生命週期的工具。
* [lerna](https://github.com/lerna/lerna): 一個用於管理 monorepos 的工具，源自於 Babel 專案。
## 用於約定式提交的工具
* [fastlane-plugin](https://github.com/xotahal/fastlane-plugin-semantic_release): 遵守規範來慣例版本並自動產生更新日誌。
* [php-commitizen](https://github.com/damianopetrungaro/php-commitizen): 一個用於建立遵循約定式提交規範的提交說明的工具。
可設定且可作為 PHP 專案中 composer 的依賴，或是對非 PHP 的專案中可以全域使用。
* [conform](https://github.com/autonomy/conform): 一個可以對 git 原始碼倉庫加上規則的工具，包含約定式提交。
* [standard-version](https://github.com/conventional-changelog/standard-version): 基於 GitHub 的新 squash 按鈕與推薦的約定式提交工作流程，自動化版本與 CHANGELOG 管理。
* [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): 提供可擴充的基於上下文或樣板的自動補全或檢查 VCS 提交視窗中約定式提交。可在所有 [JetBrains IDE](https://www.jetbrains.com/) 中使用。
* [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): 為 [JetBrains 編輯器](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...) 提供約定式提交支援。
* [commitsar](https://github.com/commitsar-app/commitsar): 用於確認分支上的提交是否符合約定式提交的 Go 工具。並提供 Docker 鏡像以供 CI 使用。
* [semantic-release](https://github.com/semantic-release/semantic-release): 自動化整個軟體包的釋出流程，提供包含：判斷下一個版本編號、產生更新日誌以及發佈軟體包。
* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): 為 VSCode 提供約定式提交支援。
## 使用約定式提交的專案
* [yargs](https://github.com/yargs/yargs): 廣受喜愛的指令參數解析器。
* [istanbuljs](https://github.com/istanbuljs/istanbuljs): 一套為 JavaScript 測試加上測試覆蓋率的開源工具與函式庫。
* [uPortal-home](https://github.com/UW-Madison-DoIT/angularjs-portal) 與 [uPortal-application-framework](https://github.com/UW-Madison-DoIT/uw-frame): 用於增強 [Apereo uPortal](https://www.apereo.org/projects/uportal) 的可選使用者介面。
* [massive.js](https://github.com/dmfay/massive-js): 一個用於 Node 與 PostgreSQL 的資料存取函式庫。
* [electron](https://github.com/electron/electron): 用 JavaScript、HTML 與 CSS 建立跨平台的桌面應用程式。
* [scroll-utility](https://github.com/LeDDGroup/scroll-utility): 一個用於置中元素與平滑動畫的捲動畫面套件。
* [Blaze UI](https://github.com/BlazeUI/blaze): 無框架開源 UI 套件。
* [Monica](https://github.com/monicahq/monica): 一個開源的人際關係管理系統。
* [mhy](https://mhy.js.org): 一個無需設定、可以直接使用、多用途的工具箱與開發環境。
* [@thi.ng/umbrella](https://github.com/thi-ng/umbrella): ~100 個 TypeScript 專案的 Monorepo，用於進行資料導向開發
* [yii2-basic-firestarter](https://github.com/HunWalk/yii2-basic-firestarter): 🔥 加強版的 Yii2 應用程式樣板。
* [dcyou/resume](https://github.com/dcyou/resume): 😎 用於簡易且快速建立線上 CV 的樣板。
* [Nintex Forms](https://www.nintex.com/workflow-automation/modern-forms/): 簡單地建立動態的線上表單以截取並送出精確與目前的資料。
* [Tina CMS](https://tinacms.org):用於為你的網站加上前端內容管理的開放原始碼工具包。
* [Uno Platform](https://platform.uno): 馬上使用 C# 與 XAML 建立移動端、桌面程式與 WebAssembly 應用程式。開放原始碼並有專業支援。
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
_想讓你的專案出現在列表中嗎？_ [發送 pull request](https://github.com/conventional-changelog/conventionalcommits.org/pulls) 吧。

15
themes/conventional-commits/layouts/about/single.html Normal file
View File

@ -0,0 +1,15 @@
<!DOCTYPE html>
<html>
{{- partial "head.html" . -}}
<body class="conventional-commits--loading">
{{- partial "header.html" . -}}
{{- partial "mini_welcome.html" . -}}
<main>
<article class="container markdown-body">
{{.Content}}
</article>
</main>
{{- partial "footer.html" . -}}
{{- partial "scripts.html" . -}}
</body>
</html>

9
themes/conventional-commits/layouts/partials/header.html
View File

@ -1,6 +1,8 @@
<header class="header">
<div class="container">
<a href="/"><div class="logo"></div></a>
<a href="/">
<div class="logo"></div>
</a>
<ul class="header__menu">
<li class="header__menu-item dropdown">
<button class="dropdown__label">Versions</button>
@ -19,6 +21,11 @@
{{ end }}
</ul>
</li>
<li class="header__menu-item dropdown">
<button class="dropdown__label">
<a href="/en/about" class="no-style-a">About</a>
</button>
</li>
</ul>
</div>
</header>

6
themes/conventional-commits/layouts/partials/mini_welcome.html Normal file
View File

@ -0,0 +1,6 @@
<section class="welcome">
<div class="mini_container">
<h1 class="welcome__title">{{.Param "Title"}}</h1>
<p class="welcome__description">{{.Param "Description"}}</p>
</div>
</section>

6
themes/conventional-commits/static/css/scss/base/_base.scss
View File

@ -49,3 +49,9 @@ article {
padding-bottom: $gap-lg - $gap-sm;
}
}
.no-style-a {
text-decoration: none;
color: white;
}

16
themes/conventional-commits/static/css/scss/layout/_welcome.scss
View File

@ -17,6 +17,22 @@
color: $color-neutral-light;
}
.mini_container {
position: relative;
z-index: 2;
display: flex;
flex-direction: column;
justify-content: center;
min-height: $welcome-min-height;
color: $color-neutral-light;
width: 100%;
max-width: $desktop-width;
margin-left: auto;
margin-right: auto;
padding-left: $gap-md;
padding-right: $gap-md;
}
&__title {
font-size: 2.6em;
margin-bottom: $gap-sm;