Skip to content

Issues: tourist-doc/tourist-core

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

10 Open 14 Closed
10 Open 14 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

When resolving a tour, do not call exec git more than once per file
#22 opened Jun 9, 2019 by J-Fields
Use spawn() instead of exec() and process git diff as a stream
#20 opened Jun 9, 2019 by J-Fields
Allow for a single tourstop to be resolved
#19 opened Jun 9, 2019 by J-Fields
Consider allowing broken tourstops (with their original location & commit intact) to be saved in a tour file enhancement New feature or request
#17 opened May 22, 2019 by J-Fields
Better error message when spawning git fails
#12 opened May 13, 2019 by J-Fields
Add more data-access methods to Tourist enhancement New feature or request
#10 opened Apr 9, 2019 by hgoldstein95
Repository tags for tour enhancement New feature or request
#9 opened Apr 9, 2019 by hgoldstein95
Consider more complicated tour structures enhancement New feature or request
#8 opened Apr 6, 2019 by J-Fields
Tourist manual
#5 opened Apr 2, 2019 by hgoldstein95
Consider allowing broken relative tourstops
#4 opened Apr 2, 2019 by J-Fields
ProTip! Mix and match filters to narrow down what you’re looking for.