You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Today I created a new folder and opened Atom in it, intending to start working on a new Git repository. So I clicked on the 0 files icon and then tried to init a repository. Instead of populating the location field with the project I had opened, it defaulted to %USERPROFILE%\github.
Steps to Reproduce
Open a folder in Atom that is not a Git repository
Try to init through the github package
Expected behavior: Field should be pre-populated with current project path
Actual behavior: Populated with C:\Users\<username>\github
Having to enter the project name seems unexpected and in my case I just clicked on "Init" without paying attention which then created a Git repo with all my projects in the parent github directory.
Would it be possible to skip the second step? So if you click on the "Create repository" button, it would initialize in the current directory without having to type the path.
Would it be possible to skip the second step? So if you click on the "Create repository" button, it would initialize in the current directory without having to type the path.
Activity
simurai commentedon Jan 4, 2018
Ran into this too. Here a gif:
Having to enter the project name seems unexpected and in my case I just clicked on "Init" without paying attention which then created a Git repo with all my projects in the parent
githubdirectory.Would it be possible to skip the second step? So if you click on the "Create repository" button, it would initialize in the current directory without having to type the path.
winstliu commentedon Jan 4, 2018
This seems logical.
smashwilson commentedon Apr 5, 2020
This was fixed in #1627 and we just didn't notice the issue link 😄