Renames all readme files to README #380
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
paschalidi
changed the title
eahefnawy
approved these changes
Apr 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
👋 hello people ☮️. I was looking those great examples you people have created. Thanks for taking such a good care and putting all these effort in order to explain and explore all these different possibilities
serverlesscan provide.I wanted to help keep the code base a little bit more uniformed. I have notices that three examples have not the same naming format on the README file. To be more explicit
aws-node-puppeteerhas it asreadme.mdaws-node-vue-nuxt-ssrhas it asreadme.mdandaws-node-oauth-dropbox-apihas it asReadMe.md.Please have a look at this issue #379
Hope this helps you a little bit with your hard work.