Initial documentation and code

Azure / platform-chaos-cli

A tool for introducing chaos into PaaS offerings using configurable extensions

MIT License

8 stars 5 forks source link

Initial documentation and code #1

Closed bengreenier closed 6 years ago

bengreenier commented 6 years ago

Description

This adds:

a nice readme 📝
initial code from original repository
github templates 💄

Checklist for success

[x] This change isn't already implemented by a pending pull request
[x] This change is a child commit of a reasonably recent commit in the master branch
- Requests need not be a single commit, but should be a linear sequence of commits (i.e. no merge commits in your PR)
[x] All tests pass locally (see the testing section for more info)
[ ] All New behaviors or major functional changes have tests

bengreenier commented 6 years ago

@Azure/platform-chaos this technically breaks our own PR guidelines as it doesn't include adequate testing. I don't have the bandwidth to implement those at this moment, does anyone else? Or does anyone have feedback on how we should best proceed?

Can i get a 👍 for block on testing, and a 👎 for ship without tests and circle back

trstringer commented 6 years ago

I personally think that we should block on testing, even if that means forward progress is put on hold until that happens. It'll only get harder to integrate proper testing.

@gavination do you have any cycles to work on this? Perhaps we can work together on it.

gavination commented 6 years ago

@trstringer, I sure do! I'm more than happy to work on it together. It'll be good insight to get a proper testing structure in early.

bengreenier commented 6 years ago

@trstringer I know you aren't the biggest standard fan, but most of the project's code conformed to that style so that is the linter configuration @gavination and I went with. Hope that makes sense 😸

trstringer commented 6 years ago

Hehehe makes total sense!!