[](#contributors-) ## Contributors ✨ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):

emrekiciman 💻	Amit Sharma 💻	Adam Kelleher 💻 🖋	Tanmay Kulkarni 💻 📖	Aleksandar Jovanovic 💻	nate giraldi 📖 💻	Julen Corral 💻
Baran Toppare 📖	EgorKraevTransferwise 💻	Ryan Russell 📖	MichaelMarien 💻 📖	Kailashbuki 💻 📖	Peter Götz 💻 📖	Patrick Blöbaum 💻 📖
Ilias Tsoumas 💻	Eli Y. Kling 📖	Andreas Stöffelbauer 💻	Ezequiel Smucler 💻	Amey Varhade 💻	Bhargav Kowshik 💻	Chris Trevino 💻
Jeffrey Gleason 💻	Ikko Ashimine 📖	Elias 💻	Padarn Wilson 💻	Michael Oberst 💻	Michael Klesel 💻	Moritz Freidank 💻
St John Grimbly 💻	Lukas Heumos 💻	Dr. Di Prodi 💻	Priyadutt 💻	drawlinson 💻	Dylan W 💻	Víctor Quintas-Martínez 💻
Rahul Shrestha 💻

## Contributing Guide This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. This Project welcomes contributions, suggestions, and feedback. All contributions, suggestions, and feedback you submitted are accepted under the [Project's license](./LICENSE). You represent that if you do not own copyright in the code that you have the authority to submit it under the [Project's license](./LICENSE). All feedback, suggestions, or contributions are not confidential. There are multiple ways to contribute to DoWhy. You can help us make DoWhy better, * Adding a Jupyter notebook that describes the use of DoWhy for solving causal problems * Helping implement a new method for any of the four steps of causal analysis: model, identify, estimate, refute * Integrating DoWhy's API with external implementations for any of the four steps, so that external libraries can be called seamlessly from the `identify_effect`, `estimate_effect` or `refute_estimate` methods. * Helping extend the DoWhy API so that we can support new functionality like interpretability of the estimate, counterfactual prediction and more. * Helping update the documentation for DoWhy If you would like to contribute, you can raise a pull request. If you have questions before contributing, you can start by opening an issue on Github. The Project abides by PyWhy's [code of conduct](https://github.com/py-why/governance/blob/main/CODE-OF-CONDUCT.md) and [trademark policy](https://github.com/py-why/governance/blob/main/TRADEMARKS.md). --- Part of MVG-0.1-beta. Made with love by GitHub. Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).