semver
Here are 661 public repositories matching this topic...
-
Updated
Apr 6, 2022 - JavaScript
-
Updated
Apr 6, 2022 - Rust
-
Updated
Mar 31, 2022 - Go
Description
I have pre-commit hooks to enforce LF line endings, this fails on every commitizen commit as it writes CRLF on windows. An option to configure this would be good.
Possible Solution
Hacky, but I have customized my local commitizen and found all instances of open and added newline='\n' to them if they are w opens. And option in the .cz.yaml to specify this would be the o
-
Updated
Nov 30, 2021 - Go
-
Updated
Dec 21, 2021 - Go
-
Updated
Apr 5, 2022 - JavaScript
-
Updated
Apr 7, 2018 - JavaScript
-
Updated
Mar 24, 2022 - TypeScript
-
Updated
Mar 16, 2022 - JavaScript
-
Updated
Apr 4, 2022 - PHP
Currently the change folder is at (getWorkspaceRoot(cwd) || gitRoot)/change.
This is typically <repo root>/change
It would be great to have a configuration option to set this, to allow something like:
<repo root>/common/changeFiles/
A configuration option could look something like:
| Option | Type | Alias | Default | Option Type | Description |
|---|---|---|---|---|---|
| changeFold |
-
Updated
Feb 24, 2022 - Python
Improve logging
Actually, the logging is made by standard version, we should first disable it and log ourself the following events:
- bump version from
{from}to{to} - output changes in
{projectRoot}/{path-to-changelog}.md - commit created
- tag
{tag}created - push success (if git push occurred)
- run postTargets
{postTargets} - postTarget
{postTargetName}failure - postTarget `{postTarge
-
Updated
Mar 13, 2022 - Go
-
Updated
Jan 6, 2022 - Shell
-
Updated
Feb 21, 2022 - C++
-
Updated
Nov 13, 2020 - Swift
-
Updated
Apr 10, 2020 - C
[DOCS] Add man page
-
Updated
Jan 15, 2022 - PHP
-
Updated
Mar 27, 2022 - Java
see discussion in jgitver/jgitver-maven-plugin#173
Improve this page
Add a description, image, and links to the semver topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the semver topic, visit your repo's landing page and select "manage topics."
Most of the documentation has been rewritten recently. The content minimum content we need is there but there is a lot that can be done to improve it.
If you'd like to contribute to the semantic-release project, helping with the following would be much appreciated: