Skip to content

Commit 3920bd0

Browse files
KrzysztofPaRomuloOliveira
authored andcommitted
Add polish language
1 parent 6d40329 commit 3920bd0

File tree

2 files changed

+490
-4
lines changed

2 files changed

+490
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ It may help you to learn what a commit is, why it is important to write good mes
2424
- [ελληνικά](README_gr-GR.md)
2525
- [Française](README_fr-FR.md)
2626
- [پارسی](README_fa-IR.md)
27+
- [Polish](README_pl-PL.md)
2728

2829
## What is a "commit"?
2930

@@ -263,10 +264,10 @@ This section is a **TL;DR** of Atlassian's excellent tutorial, ["Merging vs. Reb
263264

264265
I particularly prefer to rebase over merge. The reasons include:
265266

266-
* It generates a "clean" history, without unnecessary merge commits
267-
* _What you see is what you get_, i.e., in a code review all changes come from a specific and entitled commit, avoiding changes hidden in merge commits
268-
* More merges are resolved by the committer, and every merge change is in a commit with a proper message
269-
* It's unusual to dig in and review merge commits, so avoiding them ensures all changes have a commit where they belong
267+
- It generates a "clean" history, without unnecessary merge commits
268+
- _What you see is what you get_, i.e., in a code review all changes come from a specific and entitled commit, avoiding changes hidden in merge commits
269+
- More merges are resolved by the committer, and every merge change is in a commit with a proper message
270+
- It's unusual to dig in and review merge commits, so avoiding them ensures all changes have a commit where they belong
270271

271272
### When to squash
272273

0 commit comments

Comments
 (0)