|
| 1 | +name: Authentication issue |
| 2 | +description: An authentication problem occurred when running a Git command. |
| 3 | +labels: ["auth-issue"] |
| 4 | +body: |
| 5 | + - type: markdown |
| 6 | + attributes: |
| 7 | + value: | |
| 8 | + Thanks for taking the time to fill out this issue! |
| 9 | +
|
| 10 | + Please answer as many of the below questions as you can - this helps us better understand what the problem is, and consequently how to resolve your problem. |
| 11 | + - type: input |
| 12 | + id: version |
| 13 | + attributes: |
| 14 | + label: Version |
| 15 | + description: | |
| 16 | + What version of Git Credential Manager are you using? |
| 17 | +
|
| 18 | + Run `git credential-manager-core --version` from a terminal to see the current version. |
| 19 | +
|
| 20 | + If you are on an older version of GCM please try updating before creating an issue as the problem you are experiencing may have already been fixed. |
| 21 | + placeholder: | |
| 22 | + ex: 2.0.8-beta+e1f8492d04 |
| 23 | + validations: |
| 24 | + required: true |
| 25 | + - type: dropdown |
| 26 | + id: os |
| 27 | + attributes: |
| 28 | + label: Operating system |
| 29 | + description: What operating system are you using? |
| 30 | + options: |
| 31 | + - Windows |
| 32 | + - macOS |
| 33 | + - Linux |
| 34 | + - Other - please describe below |
| 35 | + validations: |
| 36 | + required: true |
| 37 | + - type: input |
| 38 | + id: os-version |
| 39 | + attributes: |
| 40 | + label: OS version or distribution |
| 41 | + description: Please describe the version, CPU architecture (x64, ARM, etc), or Linux distribution you are using. |
| 42 | + placeholder: | |
| 43 | + ex: Windows 11 Pro, Monterey 12.5, Ubuntu 22.04 |
| 44 | + validations: |
| 45 | + required: true |
| 46 | + - type: dropdown |
| 47 | + id: provider |
| 48 | + attributes: |
| 49 | + label: Git hosting provider(s) |
| 50 | + description: What Git host provider are you trying to connect to? |
| 51 | + multiple: true |
| 52 | + options: |
| 53 | + - Azure DevOps |
| 54 | + - Azure DevOps Server (TFS/on-prem) |
| 55 | + - Bitbucket Cloud |
| 56 | + - Bitbucket Server/DC |
| 57 | + - GitHub |
| 58 | + - GitHub Enterprise Server |
| 59 | + - GitLab |
| 60 | + - Other - please describe below |
| 61 | + validations: |
| 62 | + required: true |
| 63 | + - type: input |
| 64 | + id: provider-other |
| 65 | + attributes: |
| 66 | + label: Other hosting provider |
| 67 | + description: If you selected "Other" above, please describe the Git host you are using. |
| 68 | + - type: dropdown |
| 69 | + id: azdo-urlformat |
| 70 | + attributes: |
| 71 | + label: | |
| 72 | + (Azure DevOps only) What format is your remote URL? |
| 73 | + description: | |
| 74 | + Tip: to see your remote URL run `git remote -v` from a terminal. |
| 75 | + options: |
| 76 | + - https://dev.azure.com/{org} |
| 77 | + - https://{org}@dev.azure.com/{org} |
| 78 | + - https://{org}.visualstudio.com |
| 79 | + - type: dropdown |
| 80 | + id: web-access |
| 81 | + attributes: |
| 82 | + label: Can you access the remote repository directly in the browser? |
| 83 | + description: | |
| 84 | + If you are unable to access the repository via a web browser then it is likely GCM will also be unable to access the repository with your user account. |
| 85 | + options: |
| 86 | + - Yes, I can access the repository |
| 87 | + - No, I get a permission error |
| 88 | + - No, for a different reason - please describe behavior below |
| 89 | + validations: |
| 90 | + required: true |
| 91 | + - type: textarea |
| 92 | + id: expected |
| 93 | + attributes: |
| 94 | + label: Expected behavior |
| 95 | + description: A clear and concise description of what your expectation are. |
| 96 | + placeholder: | |
| 97 | + ex: I am authenticated and my Git operation completes successfully. |
| 98 | + validations: |
| 99 | + required: true |
| 100 | + - type: textarea |
| 101 | + id: actual |
| 102 | + attributes: |
| 103 | + label: Actual behavior |
| 104 | + description: | |
| 105 | + A clear and concise description of what actually happens. |
| 106 | + Feel free to include screenshots of dialogs or errors here, but remember to **redact any sensitive information**! |
| 107 | + placeholder: | |
| 108 | + ex: An exception "FooException" is thrown, UI freezes, etc. |
| 109 | + validations: |
| 110 | + required: true |
| 111 | + - type: textarea |
| 112 | + id: logs |
| 113 | + attributes: |
| 114 | + label: Logs |
| 115 | + description: | |
| 116 | + To capture trace logs, set the environment variables `GCM_TRACE=1` and `GIT_TRACE=1` and re-run your Git command. |
| 117 | + If you are running inside of Windows Subsystem for Linux (WSL), you must also set an additional environment variable to enable tracing: `WSLENV=$WSLENV:GCM_TRACE`. For example: |
| 118 | +
|
| 119 | + ```shell |
| 120 | + WSLENV=$WSLENV:GCM_TRACE:GIT_TRACE GCM_TRACE=1 GIT_TRACE=1 git fetch |
| 121 | + ``` |
| 122 | +
|
| 123 | + If you are using GCM version 2.0.567 onwards you can also run `git credential-manager-core diagnose` to collect useful diagnostic information that can be attached here. |
| 124 | +
|
| 125 | + :warning: **Please review and redact any private information before attaching logs and files!** |
0 commit comments