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

Update Makefile to not error if repo was cloned using Sapling #457

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

genevievehelsel
Copy link

This changes the test Makefile target conditional to pass for Sapling cloned repos.

I was building this locally and got the error message about zip files because I cloned the repo using Sapling (https://sapling-scm.com) which uses a .sl directory at the repo root as opposed to a .git directory. Getting around the message was just making an empty top level .git directory, but IMO it shouldn't show this error in this case.

As of now, this would also fail with for Mercurial cloned repos (which uses a .hg directory). I thought of generalizing it to check for any hidden top level directory, but technically .git can be a can be a text file (see: https://git-scm.com/docs/gitrepository-layout), so didn't go that route.

Also, I opted to not change the message printed in the failure case to mention Sapling or .sl as it might cause more confusion than benefit.

This changes the `test` Makefile target conditional to pass for Sapling cloned repos.

I was building this locally and ran into this issue because I cloned the repo using Sapling (https://sapling-scm.com) which uses a `.sl` directory at the repo root as opposed to a `.git` directory, and as such got the error message about zip files. Getting around the message was just making an empty top level `.git` directory, but IMO it shouldn't show this error in the first place.

As of now, this would also fail with for Mercurial cloned repos (which uses a `.hg` directory). I thought of generalizing it to check for any hidden top level directory, but technically `.git` can be a can be a text file (see: https://git-scm.com/docs/gitrepository-layout)

Also, I opted to not change the message printed in the failure case to include this as it might cause more confusion than benefit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant