Include Git Username and Email Setup In Initial Workspace Setup
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git
- Domain
- developer-experience
Research direction
Start by reviewing the initial workspace setup flow and the source control tab where the first commit fails. Determine how Git identity configuration is handled for a new workspace and define the prompt and persistence behavior. Done means a newly created workspace can make its first commit without requiring terminal commands.
Written by the indexing model from the issue text.
Description
When I create a new workspace and start doing work in it, the first time I try to commit my code in Git using the source control tab on the left side of the IDE, it fails because my username and email haven't been set up in the git executable for that workspace.
This means I have to go to terminal and run the commands:
git config --global user.email "[email protected]"
git config --global user.name "Firstname Lastname"
I feel that, if the user were prompted for this information during setup of the workspace, there wouldn't be a need for a user to drop into the terminal and run UNIX CLI commands to complete their workspace setup.
Right now I work around this by running a custom script upon creating a new workspace.
- Dominant language
- No language data
- Stars
- 35
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-builder-feedback
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
forcedotcom/code-builder-feedback#273 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
forcedotcom/code-builder-feedback#265 · 2 comments ·
-
type:enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
forcedotcom/code-builder-feedback#262 · 1 comment ·
All issues in forcedotcom/code-builder-feedback
Similar issues
-
documentation from-review-extraction github-actions priority: low severity:nit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
LearningCircuit/local-deep-research#6946 ·
Maintainers usually reply within 1 day
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#442309 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
alunduil/zfs-replicate#730 ·
Maintainers usually reply within 1 day
-
infrastructure
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
alunduil/siren-json.hs#232 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
alunduil/alunduil-infrastructure#629 ·
Maintainers usually reply within 1 day