[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Allura/SourceForge to Gitlab migration
From: |
Carl Sorensen |
Subject: |
Re: Allura/SourceForge to Gitlab migration |
Date: |
Mon, 9 Apr 2018 21:51:43 +0000 |
User-agent: |
Microsoft-MacOutlook/10.b.0.180311 |
On 4/9/18, 3:43 PM, "Karlin High" <address@hidden> wrote:
I wasn't clear on whether the free-Gold-tier-for-open-source was
automatic for any public repository, or if it needed GitLab approval. So
I tried it out, and the paid-version "squash and merge" feature IS
available in public repositories under the free-version. Here I made a
branch with multiple commits, adding 1 file and changing 1 file. Then I
did a squash-and-merge.
<https://gitlab.com/karlinhigh/squashtest/commits/master>
Result here; comments on whether the presentation is satisfactory? There
were opportunities to add more commit messaging, so lack of that is my
fault, not GitLab's.
The problem with this workflow is that the merger is the person who needs to do
the squash-and-merge. That's extra work for the merger. I'd prefer to keep
the work on the patch creator.
The current workflow is that the patch author does the squash, and then we
don't do a merge, we do a regular commit.
The only merge commits in our current workflow, IIUC, are translation merges.
Thanks,
Carl
- Re: Allura/SourceForge to Gitlab migration, (continued)
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Federico Bruni, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration,
Carl Sorensen <=
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Message not available
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, James Lowe, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/10
Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09