Skip to content

Conversation

@feltnerm
Copy link

I had some troubles getting django-git working. I made some changes, and it works great now. Maybe they would be useful for others.

Specifically, I...
...fixed the requirements. It appears that the repositories for the packages in the previous requirements.txt did not exist anymore.
...modified the templates to display the repository path correctly. Originally, the templates (index.html, commit.html, and repo.html) were calling repo.path; a property that simply does not exist. In the current release (0.3.2) it states for Repo.Base:

‘working_dir’ is the working directory of the git command, wich is the working tree directory if available or the .git directory in case of bare repositories
So, yeah, they use that now.

The example project just displays all the repositories on ~/Projects/ (can be changed in example/settings.py), and works with the changes I've made.


note to maintainer:
Apologies if I did this incorrectly (first pull request and all..). I'm branching out from my fork's master because I'm trying to continue adding changes, so I've changed the pull request to reference this branch (GitPython0.3.2) which will have all the fixes I've included above.

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