-
Notifications
You must be signed in to change notification settings - Fork 5
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
tests don't work when run without git repository #48
Comments
By the way, I'm on PyConPL till Sunday so feel free to ping me and we can meet and discuss it. |
Yes let's do that!! Not sure why this is happening at a first glance tbh. Let's meet up and we can look into it 🤝 |
I think we should discuss this. For operations like
And in situations where you need a git repository for example for getting a list of files with conflicts, the app should look for git repository to which the file belongs to instead of the one in CWD. Let's say I have a git repo in /foo/bar/ and a file with conflict in /foo/bar/notebooks/file.ipynb and I run the tool from /tmp - the tool should find the repo in /foo/bar. But the main question is, why do you need a repository at all? I think it can be necessary only for the new diff command but meta, assert, fix and show commands don't need it at all. |
That's a good point. We always look for git repos by default to look for config files (look until the repo root and if there's no
That would be the case for
Completely agree. There is an implementation for finding the common parent (in case you pass different paths) and looking for the repo root there but I don't think we're using it everywhere (which we definitely should). So summary of changes:
|
Done!! And thanks for the suggestion! Maybe worth double checking with you that the fixes are working? |
When packaging software for Fedora, we run tests in an unpacked archive without initialized git repository for the codebase because we are testing the installed version. Would it make sense to make the tests compatible with this way of running them?
Maybe the tests can initialize their own repositories in a tmpdir or something like that.
The current log I have is:
The text was updated successfully, but these errors were encountered: