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.

Sign up for GitHub

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

Jump to bottom

Properly handle ambigious files #37

Merged
merged 4 commits into from
Jun 17, 2020
Merged

Properly handle ambigious files #37

merged 4 commits into from
Jun 17, 2020

Conversation

fishi0x01
Copy link
Owner

Fixes #36

@fishi0x01 fishi0x01 self-assigned this Jun 14, 2020
@fishi0x01 fishi0x01 force-pushed the fix-ambigious-file branch from 5ce8e10 to 8a96f82 Compare June 14, 2020 13:35
@fishi0x01 fishi0x01 added the bug Something isn't working label Jun 14, 2020
@fishi0x01 fishi0x01 force-pushed the fix-ambigious-file branch 2 times, most recently from 07d7143 to 2adaf13 Compare June 16, 2020 19:53
@fishi0x01 fishi0x01 force-pushed the fix-ambigious-file branch from 2adaf13 to a99a2af Compare June 17, 2020 19:28
@fishi0x01 fishi0x01 marked this pull request as ready for review June 17, 2020 19:54
@fishi0x01 fishi0x01 merged commit 8fbc0eb into master Jun 17, 2020
@fishi0x01 fishi0x01 deleted the fix-ambigious-file branch June 17, 2020 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@fishi0x01 fishi0x01

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Properly handle ambigious files
1 participant
@fishi0x01