-
[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) and [Semantic Release](https://github.com/semantic-release/semantic-release) provide a way to objectively assign versions and aut…
reece updated
1 month ago
-
## Describe the bug
Python semantic release introduced recursive parsing of commits for change logs.
At the moment the default behaviour of the team is to use squash merges into develop and pul…
-
- https://www.conventionalcommits.org/en/v1.0.0/#summary
- https://github.com/semantic-release/semantic-release
-
-
### Current behavior
- Committed changes to feature branch that is by mistake behind main branch.
- Commit analyser says that the branch is behind so no new version is released
- Merged from main t…
-
ORT Server project currently uses a commit convention that looks like [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), but the convention does not semantically adhere to Convent…
-
In this project all pieces are versioned using semantic commits.
So it is mandatory to use semantic syntax in the commits in order to generate new version for the components.
- [ ] Investigate how t…
-
# emoji-semantic-commits
emoji based semantic
## Why?
That's at least 3 chars less for the title 🥳, plus it's quite fun and 😎
## Proposal
Emoji based semantic commits as:
* ⭐️ **feat**…
-
## Tools for semantic commits 🛠️
There are several tools that can assist you in writing semantic commits, such as:
- **Commitizen**: A CLI tool that helps you write interactive semantic commits.…
-
Support for semantic commits seems to be easy to implement. See https://seesparkbox.com/foundry/semantic_commit_messages
-
I am trying to create a migration notes section for the next generated semantic-release with the help of semantic-release based on the merge-request description of the last commits.
it works with m…