Since we follow Conventional Commits, we're able to automatically create formal "releases" of the website based on our commit messages. Releases in the context of websites are simply snapshots in time of the website content. We use Commitizen to automatically create these releases using SemVer as the version numbering scheme.
Because releases are created based on commit messages, a new release is created quite often---sometimes several times in a day. This also means that any individual release will not have many changes within it. Below is a list of the releases we've made so far, along with what was changed within each release.
- ✏️ correct internal links to files (#110)
- 🚚 merge motivations and risks into overview (#109)
- ✏️ wrong paths to design files (#108)
- 🚚 move around design to be multiple chapters (#107)
- ✨ guide on collaborating on DST (#100)
- ✨ section on one team has one product design (#101)
- 🏗️ naming convention for repos (#97)
- 🐛 forgot to add collaborating landing page (#99)
- ♻️ split the contributing and collaborating into two parts (#98)
- 🐛 correct URLs after running lychee checker
- ✨ add responsibilities and expectations of tech leads (#75)
- ✨ convert to book format (#67)
- ✨ add CONTRIBUTING document (#64)
- ✨ expand on README with contributing and badges section (#63)
- ♻️ move miletstones to below deliverables