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:

Merge request, review, discussion:

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.



"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."


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:

Code, with inline or side-by-side diffs. Option to hide or show comments inline with the code:

And they have this "pipeline" feature, which appears to be automated tests.


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

lilypond-devel mailing list

Reply via email to