-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add community documentation #23
Closed
Closed
Conversation
This file contains 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
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
- [ ] Check that nothing drastic happened in the package.json - [ ] Check the package.json description - it didn't match the GitHub description for the repository. - [ ] Check the `package.json` keywords. We added some from your GitHub topics. - [ ] Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work. - [ ] If there are more contirbutors, add them to the Contributors field in the `package.json`. - [ ] Add some tests! There aren't any currently set.
Let's pretend this never happened. |
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.
Dearest humans,
You are missing some important community files. I am adding them here for you!
Here are some things you should do manually before merging this Pull Request:
package.json
keywords. We added some from your GitHub topics.,Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work.,If there are more contirbutors, add them to the Contributors field in thepackage.json
.,Add some tests! There aren't any currently set.package.json
keywords. We added some from your GitHub topics.,Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work.,If there are more contirbutors, add them to the Contributors field in thepackage.json
.,Add some tests! There aren't any currently set.package.json
keywords. We added some from your GitHub topics.,Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work.,If there are more contirbutors, add them to the Contributors field in thepackage.json
.,Add some tests! There aren't any currently set.package.json
keywords. We added some from your GitHub topics.,Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work.,If there are more contirbutors, add them to the Contributors field in thepackage.json
.,Add some tests! There aren't any currently set.package.json
keywords. We added some from your GitHub topics.,Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work.,If there are more contirbutors, add them to the Contributors field in thepackage.json
.,Add some tests! There aren't any currently set.package.json
keywords. We added some from your GitHub topics.,Check that the homepage in the package.json is OK. Another one besides your GitHub repo might work.,If there are more contirbutors, add them to the Contributors field in thepackage.json
.,Add some tests! There aren't any currently set.