Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
travis encrypt --add destroys file formatting #651
But it's really annoying and completely beats the purpose of automated writing to the file if it destroys the formatting in the process.
Since it only has to check if the given field is present and overwrite it, or if not present append the field to the end of file, I don't think this needs a full parser reimplementation, and probably should be handled as its own case.
Let me now if this sounds reasonable to you.
This is a serious problem. If nothing else, the
The documentation says nothing about this behavior, and it's really problematic. I think the number of issues that have been opened about it should be a decent indicator of how serious this is to people.
In my case, I had some blocks written, but commented out (temporarily). I hadn't yet committed my changes, and
And to those who think, "well you should have committed first", you may be right. I still think that it's unacceptable for
It's quite surprising that a command to
For individuals that are setting up and committing what a given secure key does within
If you are unable to write your own parser to preserve the comments then just have a command such as