[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Allura/SourceForge to Gitlab migration
From: |
Karlin High |
Subject: |
Re: Allura/SourceForge to Gitlab migration |
Date: |
Tue, 10 Apr 2018 11:12:05 -0500 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 4/10/2018 8:54 AM, Karlin High wrote:
I was also looking for good examples of issues and "boards" displaying
issue status, and code review and discussion.
Here's the GitLab for the GNOME Nautilus file manager.
Issue board:
<https://gitlab.gnome.org/GNOME/nautilus/boards>
Merge request, review, discussion:
<https://gitlab.gnome.org/GNOME/nautilus/merge_requests/187>
Notable: "Request to merge... into master (20 commits behind)
Below that: "Fast-forward merge is not possible. To merge this request,
first rebase locally."
Apparently there is a project-level setting that can require all merges
be fast-forward, requiring a re-base before merge if the target branch
has moved ahead.
<GITLAB>
<https://docs.gitlab.com/ee/user/project/merge_requests/fast_forward_merge.html>
"When the fast-forward merge (--ff-only) setting is enabled, no merge
commits will be created and all merges are fast-forwarded, which means
that merging is only allowed if the branch could be fast-forwarded...
When a fast-forward merge is not possible, the user is given the option
to rebase."
</GITLAB>
Perhaps that would be getting fairly close to current practices?
Back to GNOME Nautilus on GitLab...
Here's a merge request under discussion. Looks like there are different
views available, focusing on the discussion or on the code.
Discussion, allows showing or hiding details with quoted code:
<https://gitlab.gnome.org/GNOME/nautilus/merge_requests/187>
Code, with inline or side-by-side diffs. Option to hide or show comments
inline with the code:
<https://gitlab.gnome.org/GNOME/nautilus/merge_requests/187/diffs>
And they have this "pipeline" feature, which appears to be automated tests.
<https://gitlab.gnome.org/lamefun/nautilus/pipelines/7548/builds>
It shows console output...
Failed job: <https://gitlab.gnome.org/lamefun/nautilus/-/jobs/19606>
Successful job: <https://gitlab.gnome.org/lamefun/nautilus/-/jobs/19611>
Job history: <https://gitlab.gnome.org/GNOME/nautilus/-/jobs>
Now, if that thing could be taught to do the LilyPond "make, make check,
make doc" routine...
--
Karlin High
Missouri, USA
- Re: Allura/SourceForge to Gitlab migration, (continued)
- 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, 2018/04/09
- 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 <=
- 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