Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Serverless overwrites existing ignore file
See original GitHub issueThis is a Bug Report
Description
My existing .gitignore file was overwritten when I ran serverless create --template aws-nodejs. I expected that Serverless would append to any existing file.
No error message was reported, I noticed when I went to commit Serverless’ changes that it had overwritten the existing .gitignore file.
Yes, this happened when I started a new project but there was an existing ignore file because I’m using Vagrant; I’d already committed the Vagrantfile and added the .vagrant folder to the .gitignore file. This is actually the first time I’ve used Serverless (but this issue seemed like something you’d want to know about).
Similar or dependent issues: I didn’t notice any when I searched.
Additional Data
- Serverless Framework Version you’re using: v1.12.1
- Operating System: Ubuntu 16.04 LTS Server (in a Vagrant-built VirtualBox VM hosted by OS X 10.11)
- Stack Trace: N/A
- Provider Error messages: N/A
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Probably should check if you want to merge or replace or do nothing.
Closing since this issue is quite old and there are no future plans to change the behavoir of this in the foreseeable future.