Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(fi): translate section: "Why Use Conventional Commits" #13

Merged
merged 7 commits into from
Nov 25, 2022
Merged

feat(fi): translate section: "Why Use Conventional Commits" #13

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
50f7fa7
feat(fi): translate 'Why Use Conventional Commits' headline
masisoranummi Nov 21, 2022
0b1330f
feat(fi): translate first line of 'Why Use Conventional Commits'
masisoranummi Nov 21, 2022
1cff78f
feat(fi): translate second line of 'Why Use Conventional Commits'
masisoranummi Nov 21, 2022
212a2bb
feat(fi): retranslate second line of 'Why Use Conventional Commits'
masisoranummi Nov 21, 2022
f6dbc0b
feat(fi): translate third line of 'Why Use Conventional Commits'
masisoranummi Nov 21, 2022
7d13021
feat(fi): translate fourth line of 'Why Use Conventional Commits'
masisoranummi Nov 21, 2022
115073f
feat(fi): translate fifth line of 'Why Use Conventional Commits'
masisoranummi Nov 21, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions content/next/index.fi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,14 +132,14 @@ Avainsanat "PITÄÄ" (“MUST”), "EI PIDÄ" (“MUST NOT"), "PAKOLLINEN" (“R
1. Toteuttajien EI PIDÄ pitää tietoa tavanmukaisissa muutoksissa merkkikokoriippuvaisina, poikkeuksena BREAKING CHANGE mikä PITÄÄ olla kirjoitettu isoilla kirjaimilla.
1. BREAKING-CHANGE PITÄÄ olla samanmerkityksinen BREAKING CHANGE kanssa, kun sitä käytetään merkkinä alatunnisteessa.

## Why Use Conventional Commits

- Automatically generating CHANGELOGs.
- Automatically determining a semantic version bump (based on the types of commits landed).
- Communicating the nature of changes to teammates, the public, and other stakeholders.
- Triggering build and publish processes.
- Making it easier for people to contribute to your projects, by allowing them to explore
a more structured commit history.
## Miksi Käyttää Tavanmukaisia Muutoksia

- Automaattisesti generoidut MUUTOSLOKIT
- Automaattisesti määritely SemVerin mukainen bump (muutosten tyypistä riippuen).
- Muutosten luonteen kommunikoiminen tiimitoverille, yleisölle, ja muille sidosryhmille.
- Luonti- ja julkaisuprosessien laukaiseminen.
- Helpottaa muiden osallistumista projektiisi, antamalla heidän tutustua
hyvin organisoituun muutoshistoriaan.

## UKK (Usein kysytyt kysymykset)

Expand Down