match_tree doesn't return the symlinks regardless of the followSymlinks parameter about python-pathspec

[ftrofin]

I have a PR for this but I don't have access to this repo. Can you please give me access so I can create the PR?

[ftrofin]

@cpburnz Caleb?

[cpburnz]

@ftrofin You don't need direct access to create a pull request. Just fork the project, commit your changes there, then submit a pull request.

I think you're right that it's a bug. In my experience most programs treat symlinks as regular files if they're not resolving the target. Git, in particular, I think treats symlinks as files regardless if they point to a file or folder.

[ftrofin]

I tried that. I cloned (using https), created a branch named 'issue_31' and tried to push it back:
$ git push --set-upstream origin issue_31
remote: Permission to cpburnz/python-path-specification.git denied to ftrofin.

[cpburnz]

@ftrofin Are you familiar with how to fork and make pull requests on Github? On Github you have to use the web interface to perform those actions, not directly using git.

[ftrofin]

I didn't have to do this to repos I don't own. Here is the change, very simple, can you please apply it? Thanks!

[cpburnz]

@ftrofin I've implemented this on the master branch.

[ftrofin]

Thank you Caleb. Any idea when you're going to make a new release with the latest changes/fixes?

[cpburnz]

@ftrofin I'll be able to get to it this coming weekend.

[cpburnz]

v0.8.0 has been released which supports symlinks.