Learn to say popular changelog and release automation tool names correctly.
0 / 5 completed
1 / 5
How is Changesets (versioning and changelog tool for monorepos) correctly pronounced?
Changesets is pronounced 'CHAYNJ-sets' — 'change' plus 'sets', both plain English words. Stress on CHAYNJ. In a technical interview: "Changesets bumped the version of every affected package automatically when we merged the PR."
2 / 5
How is Semantic Release (automated versioning and package publishing tool) correctly pronounced?
Semantic Release is pronounced 'sih-MAN-tik rih-LEES' — 'semantic' (stress on MAN) plus 'release'. In a technical interview: "Semantic Release read our commit messages and decided a minor version bump was needed."
3 / 5
How is Release Please (automated release PR and changelog tool by Google) correctly pronounced?
Release Please is pronounced 'rih-LEES pleez' — 'release' plus 'please', both plain English words. In a technical interview: "Release Please opened a pull request with the changelog already drafted from our conventional commits."
4 / 5
How is Auto (release automation tool that generates changelogs from GitHub labels) correctly pronounced?
Auto (the release tool) is pronounced 'AW-toh' — exactly like the everyday shortening of 'automatic', stress on AW. In a technical interview: "Auto picked the next version number based purely on the labels attached to each merged pull request."
5 / 5
How is Conventional Commits (commit message convention used to drive changelog generation) correctly pronounced?
Conventional Commits is pronounced 'kun-VEN-shun-ul KOM-its' — 'conventional' plus 'commits', both plain English words. In a technical interview: "Conventional Commits made it possible to generate the whole changelog automatically from git history."