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

Add Git installation instructions to docs #764

Closed
talmo opened this issue May 27, 2022 · 1 comment
Closed

Add Git installation instructions to docs #764

talmo opened this issue May 27, 2022 · 1 comment
Assignees
Labels
documentation This issue exists because the documentation is outdated.

Comments

@talmo
Copy link
Collaborator

talmo commented May 27, 2022

We have instructions on opening the console, installing conda, and different installation methods, but not the git CLI. This would be a good complement to the "conda from source" method.

As a reference, see the instructions for M1 Mac installation -- it's step-by-step including how to install system-wide utilities analogous to git like brew.

The git-scm Windows client is a bit intrusive of an install, but one option for Windows could be to have a PowerShell-based 1-liner like chocolatey has for their install method.


"I finally was able to install SLEAP from the source by installing "Git", otherwise there was an error telling me that "git" was not recognized. Beginners like me could experience the same, unfortunately the GUI is very important to us, thank you for improving it constantly! I stopped using DLC because of the GUI..."

Originally posted by @ARTUR551 in #754 (reply in thread)

@talmo talmo added the documentation This issue exists because the documentation is outdated. label May 27, 2022
@roomrys
Copy link
Collaborator

roomrys commented Jul 19, 2022

I added a step to conda from source installation where users first check their git version and if an error occurs, I direct them to git-scm installation docs which covers all installation methods for all OS's.

@roomrys roomrys added the fixed in future release Fix or feature is merged into develop and will be available in future release. label Jul 19, 2022
@roomrys roomrys closed this as completed Jul 25, 2022
@roomrys roomrys removed the fixed in future release Fix or feature is merged into develop and will be available in future release. label Aug 3, 2022
@roomrys roomrys self-assigned this Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This issue exists because the documentation is outdated.
Projects
None yet
Development

No branches or pull requests

2 participants