Removing a space before the pyenv file, so that when you uncomment .gitignore you recognise it #589
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…itignore you recognise it
machadoah
requested review from
filipechagas and
tediganeva5
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Update
Python.gitignoretemplateDetails
Removing the space before the pyenv file, so that when you uncomment .gitignore it recognises it.
Currently, the line in the python-version file generated by pyenv has a space in it, which means that when we uncomment it with a browser shortcut, such as control + /, the file ends up not being ignored, because it's " .python-version" and not ".python-version".