What about different commit types and then squashing and merging? #96

New Issue

GiteaMirror · 2026-02-17T11:45:21-06:00

GiteaMirror commented

2026-02-17 11:45:21 -06:00

Originally created by @jacek-jablonski on GitHub (Apr 17, 2020).

Hi!

How does different commits with different message types relate to later squashing and merging?

History on branch looks like:

fix: something
docs: add to docs
feat: added feature A

Later during squash and merge should I create completely new summarized message ignoring f.e. docs: or fix:?

Originally created by @jacek-jablonski on GitHub (Apr 17, 2020). Hi! How does different commits with different message types relate to later squashing and merging? History on branch looks like: 1. fix: something 2. docs: add to docs 3. feat: added feature A Later during squash and merge should I create completely new summarized message ignoring f.e. `docs:` or `fix:`?

GiteaMirror closed this issue

2026-02-17 11:45:21 -06:00

GiteaMirror commented

2026-02-17 11:45:23 -06:00

@damianopetrungaro commented on GitHub (Apr 20, 2020):

You should not squash merge 3 commits meant to solve 3 different problems.
You can use 3 pull request each one with 1 commit, or 1 pull request with 3 commits, both of them without squashing commits :)

@damianopetrungaro commented on GitHub (Apr 20, 2020): You should not squash merge 3 commits meant to solve 3 different problems. You can use 3 pull request each one with 1 commit, or 1 pull request with 3 commits, both of them without squashing commits :)

GiteaMirror referenced this issue

2026-02-17 11:57:24 -06:00

[PR #96] [MERGED] docs: Small spelling corrections in the ITALIAN VERSION #284

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#96