Hello folks,
I've been told that our Sysadmins have developed some tooling capable of
checking the "Squash when merging" checkbox by default for new Merge
Requests. This would be a downstream solution to
https://gitlab.com/gitlab-org/gitlab/-/issues/222175.
I'd like to propose that this be do
> [...]
> I've been told that our Sysadmins have developed some tooling capable of
> checking the "Squash when merging" checkbox by default for new Merge
> Requests. [...]
>
> I'd like to propose [squash-merge] as a sane default for new Merge
> Requests.
>
> [...]
> Thoughts?
Yes, I would like t
On Friday, 2 October 2020 18:39:37 BST Nate Graham wrote:
> Hello folks,
> I've been told that our Sysadmins have developed some tooling capable of
> checking the "Squash when merging" checkbox by default for new Merge
> Requests. This would be a downstream solution to
> https://gitlab.com/gitla
On Fri, 2020-10-02 at 11:39 -0600, Nate Graham wrote:
> Hello folks,
> I've been told that our Sysadmins have developed some tooling capable of
> checking the "Squash when merging" checkbox by default for new Merge
> Requests. This would be a downstream solution to
> https://gitlab.com/gitlab-org/g
El divendres, 2 d’octubre de 2020, a les 21:19:02 CEST, Konstantin Kharlamov va
escriure:
> On Fri, 2020-10-02 at 11:39 -0600, Nate Graham wrote:
> > Accordingly, I think squash-merging makes sense as the default value to
> > avoid this. People who are comfortable with the "curated MR commit
> > h
> > However, it remains a fairly advanced workflow which is challenging for
> > newcomers, drive-by-developers, and people not as familiar with git. For
> > these people, squash-merging makes much more sense, [...]
This workflow is too advanced for me. My commits are usually garbage like “fix
pip
On Sat, 2020-10-03 at 00:26 +0200, David Hurka wrote:
> > > However, it remains a fairly advanced workflow which is challenging for
> > > newcomers, drive-by-developers, and people not as familiar with git. For
> > > these people, squash-merging makes much more sense, [...]
>
> This workflow is to
