Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Equivalent of "git init" missing? #2883

Closed
JeffCohen opened this issue Sep 26, 2017 · 2 comments
Closed

Equivalent of "git init" missing? #2883

JeffCohen opened this issue Sep 26, 2017 · 2 comments
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs

Comments

@JeffCohen
Copy link

Description

The old version of the app allowed one to convert an ordinary folder into a repo by dragging the folder onto the app or selecting "Add Repository". In either case, the app would prompt if it should turn the folder into a repository (essentially just doing a git init), which was very helpful.

Maybe I'm missing something, but now that seems impossible. When prompted to "Create a Repository" instead, a brand new subdirectory for the repo is created, rather than running git init on the selected folder.

Version

GitHub Desktop version: 1.0.1

OS version: macOS High Sierra (also reproduced on macOS Sierra)

Steps to Reproduce

  1. Drag an ordinary folder into the app (or use Add Local Repository and choose the folder)
  2. You'll get a message saying "This directory does not appear to be a Git repository. Would you like to create a repository here instead?" and the "Add Repository" folder is disabled
  3. Click "create a repository here"
  4. You get the Create New Repository dialog (which I don't think is necessary)
  5. Enter a repo name and click Create Repository
  6. Notice that you end up with a new subfolder for the repo

Expected behavior: The chosen folder should become a repository in-place

Actual behavior: A new subfolder was created

Reproduces how often: 100%

@shiftkey
Copy link
Member

@JeffCohen thanks for the report!

Notice that you end up with a new subfolder for the repo

Yeah, this doesn't seem right. I'll see if I can re-create this issue.

@shiftkey shiftkey added bug Confirmed bugs or reports that are very likely to be bugs investigation-needed Likely bugs, but haven't been reliably reproduced by a reviewer labels Sep 26, 2017
@shiftkey shiftkey self-assigned this Sep 26, 2017
@shiftkey shiftkey removed the investigation-needed Likely bugs, but haven't been reliably reproduced by a reviewer label Sep 28, 2017
@JeffCohen
Copy link
Author

Thanks everyone! Can't wait for the next release :-)

@lock lock bot locked as resolved and limited conversation to collaborators Jul 20, 2018
@desktop desktop unlocked this conversation Sep 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

2 participants