keep gitignore & gitattributes on upgrade/rename #162
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.
fixes #37, further to #54 -- I feel that the user expects to keep the .gitignore.d/foo and .gitattributes.d/foo files in effect when renaming repo foo to bar. Currently
upgrade()
abandons the foo files and updates .git to point to bar files.I've implemented renaming the files with
mv
inupgrade()
so that even ifcore.excludesfile
orcore.attributesfile
points elsewhere, they can be moved into the recommended location.mv
will exit with an error instead of overwriting any file, and I've handled showing that to the user.I've only played with this a bit. Open for improvements.