-
-
Notifications
You must be signed in to change notification settings - Fork 799
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.
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
Merging of gitignore files regenerates file regardless of actual content change #848
Comments
Please |
Much better, the template files are still rewritten even if there aren't any changes though. btw. I figured out that I can add an en exclusion pattern in my |
Thanks, fixed. Please
|
I don't understand why do you need that :) Is |
Thanks, seems to work great. I guess this contents checking really should be As I understand it the moment I use another directory than what The handful of libraries I've tried to install so far just seems to be more or I will of course use the |
In this case, you can use Please note that you can have unlimited number of library storages. You can manage storage via
Also, you can have custom folder in the project, for example [platformio]
lib_extra_dirs = mylib And install some libs
|
What kind of issue is this?
Configuration
Operating system:
Ubuntu 16.10
PlatformIO Version (
platformio --version
):Latest release and todays develop snapshot (PlatformIO, version 3.2.0b6)
Description of problem
Even if the contents of
.gitignore
is the same the file is regenerated and possibly reordered.Steps to Reproduce
before init:
Actual Results
after init:
Expected Results
Additional info
I propose that the template
.gitignore
doesnt make any structural changes to thegitignore file if the functional conent is unchanged and that the template
renderers in general doesnt rewrite files that have the same content.
Also if a user for one reason of the other want's to override a line in
.gitignore by commenting it the gitignore merger should not readd it.
A sketchy test case data example:
The text was updated successfully, but these errors were encountered: