Change to two spaces
This commit is contained in:
parent
2537fe2052
commit
ed60ab964c
556 changed files with 2252 additions and 2252 deletions
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
title: >
|
||||
Are conventional commits worth it?
|
||||
Are conventional commits worth it?
|
||||
pubDate: 2023-11-24
|
||||
permalink: >-
|
||||
archive/2023/11/24/are-conventional-commits-worth-it
|
||||
archive/2023/11/24/are-conventional-commits-worth-it
|
||||
tags:
|
||||
- software-development
|
||||
- git
|
||||
- software-development
|
||||
- git
|
||||
---
|
||||
|
||||
For some time, I've written commit messages following the Conventional Commits specification, where you start the subject with the type of commit - such as `feat`, `fix`, `chore`, `docs`, etc - and provide an optional scope before completing the subject line (the first line in the message).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue