tvavrda
(Tomáš Vavrda)
May 5, 2021, 9:41am
1
I would propose using git squash for merging from feature branches for the following reasons:
Cleaner master git – no noise from how the development of the feature went on – a single commit for a feature
Possibility to update the final commit message – remove typos, update the description, etc.
A clear place where to put the link to a feature/bug here on community
washi
(Petr Hrehorovsky)
May 10, 2021, 10:28am
2
I think it is useful and I see cases where it is really good to do so. But I’m not sure about making it rule. The person, who is merging should be able to decide whether to squash or not.
tvavrda
(Tomáš Vavrda)
June 22, 2021, 1:53pm
3
Interesting - when using Squash the commit is made directly to the repository – without the link to the pull request.
Example squashed commit:
committed 01:50PM - 22 Jun 21 UTC
* Dockerfile build now contains rebuilding libgdiplus library to correctly displ… ay international characters inside FastReports reports.
Co-authored-by: David Pochobradský <david.pochobradsky@synergine.cz>
Original PR:
origam:master
← davidpochobradsky:master
opened 05:05PM - 21 Jun 21 UTC
Fix https://community.origam.com/t/not-displaying-c-at-the-end-of-words-in-pdf-g… enerated-from-fastreport/755
* Dockerfile build now contains rebuilding libgdiplus library to correctly display international characters inside FastReports reports.