Skip to content
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
wants to merge 13 commits into from

Conversation

RichardLitt
Copy link
Member

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:

  • Check if .travis.yml was overwritten or not.,- [ ] 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.
This was referenced Oct 3, 2017
- [ ] 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.
@RichardLitt
Copy link
Member Author

Let's pretend this never happened.

@RichardLitt RichardLitt closed this Oct 3, 2017
@RichardLitt RichardLitt deleted the docs/boost-vitality/2017-10-03 branch October 3, 2017 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant