Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3883

Incorrect user name/email in commit message after user went through Git server PAT flow in DS 3.4.0.RC-01-11

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Incorrect user name and email in commit messages for some users

      There is currently a known issue for users who are using a link:https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.6/html-single/user_guide/index#using-a-git-provider-access-token[Kubernetes Secret with their Git-provider credentials]. The user name and email for Git operations in workspaces for those users are currently taken from the `user-profile` Secret of the `__<user>__-devspaces` namespace.

      IMPORTANT: This known issue does not impact link:https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.6/html-single/administration_guide/index#configuring-oauth-for-git-providers[Git-provider OAuth that has been configured by administrators].

      .Workaround

      * In the editor terminal of the running workspace, run the following commands to set your commit author name and email:
      +
      [subs="+quotes"]
      ----
      git commit config --global user.name __<your_name>__
      git commit config --global user.email __<your_email>__
      ----
      Show
      = Incorrect user name and email in commit messages for some users There is currently a known issue for users who are using a link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.6/html-single/user_guide/index#using-a-git-provider-access-token [Kubernetes Secret with their Git-provider credentials]. The user name and email for Git operations in workspaces for those users are currently taken from the `user-profile` Secret of the `__<user>__-devspaces` namespace. IMPORTANT: This known issue does not impact link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.6/html-single/administration_guide/index#configuring-oauth-for-git-providers [Git-provider OAuth that has been configured by administrators]. .Workaround * In the editor terminal of the running workspace, run the following commands to set your commit author name and email: + [subs="+quotes"] ---- git commit config --global user.name __<your_name>__ git commit config --global user.email __<your_email>__ ----
    • Known Issue
    • Done
    • Workaround Exists
    • Hide

      Set correct commit author name and email inside running workspace by executing next commands in editor terminal:

      git commit config --global user.name "your name"
git commit config --global user.email "your email"
      Show
      Set correct commit author name and email inside running workspace by executing next commands in editor terminal: git commit config --global user.name "your name" git commit config --global user.email "your email"

      Description of problem:

      When execute commit/push after launching a factory on gitlab server there is observated a confusing name/email.
      Actually the name looks as 'expecting', because is obtained from 'user-profile' Secret of <user>-devspaces namespace. But in the same time it's a bit confused

      Prerequisites (if any, like setup, operators/versions):

      -DS 3.4.0.RC-01-11
      -gitlab server with test repository available to launch a factory
      -configured PAT

      Steps to Reproduce

      -launch a factory
      -make git commit and push
      -watch username and email in terminal
      (git config --list)

      Actual results:

      Data from 'user-profile' secret

      PAT
      user.name=admin
user.email=admin@che

      Expected results:

      Reproducibility (Always/Intermittent/Only Once):

      Always

       

            ibuziuk@redhat.com Ilya Buziuk
            askadam1 ashwini kadam
            Max Leonov Max Leonov
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: