Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
options to avoid .upignore to pickup .gitignore by default? #557
Just started to use
Was thinking if it is more intuitive to have
Furthermore, it helps to make it more explicit and doesn't need to check two files when it comes confirming the settings.
can be very useful to have the feature as a separate module to make it possible to add
I'd totally agree from a UX perspective that it can be confusing, my main concern is included sensitive files by accident which would normally be gitignored.
Definitely open to suggestions there, maybe it would be possible to make missing files a bit easier to troubleshoot, right now there's just
was thinking of possibly using "index" field in the config file so that it could be checked before deploy? currently for Node it seems the run command would rely on "start" command in the
I tend to agree with this. What you explicitly store in the repo isn't necessarily what you are trying to package for a deployment to Lambda. I'd say that a lot of projects beyond simple examples will have some kind of build step, which would result in output that would most likely be in
I don't know how many times i've bashed my head on the keyboard because my deployment didn't work and then, aha! .upignore!
I see a few options here: