[Bug 58595] New: gitlab fails to run rebase builds due to missing contributor name

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58595

            Bug ID: 58595
           Summary: gitlab fails to run rebase builds due to missing
                    contributor name
           Product: WineHQ Gitlab
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gitlab-unknown
          Assignee: wine-bugs(a)winehq.org
          Reporter: hibbsncc1701(a)gmail.com
      Distribution: ---

When I attempted to rebase MR 8679 to current git via the web UI the build
failed with an error stating that it did not have a valid committer name.

This is despite my name and email address being defined in my gitlab profile
and my gitlab settings being set to use the primary email for the web UI
actions.

The log also indicates that it failed to use my email address instead
defaulting to the gitlab runner name.

Build log: https://gitlab.winehq.org/hibbsncc1701/wine/-/jobs/180801

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 58595] gitlab fails to run rebase builds due to missing contributor name

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58595

--- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> ---
That's because your MR contains a merge commit. Don't do that, use git rebase
instead.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 58595] gitlab fails to run rebase builds due to missing contributor name

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58595

--- Comment #2 from Patrick Hibbs <hibbsncc1701(a)gmail.com> ---
Got it. It looks like that merge commit was made by the gitlab UI, it didn't
exist in my local tree, and rebasing on my local system and force pushing it
allowed the build to succeed. (with the flaky test failures.)

Maybe the Git Tutorial should be updated to warn people not to use the gitlab
UI when rebasing an MR? There's nothing mentioned about gitlab's UI causing
failures.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.