Thank you for your interest in contributing to inview‑club/devops-cases! 🎉
This project is a collection of DevOps cases for learning, and we welcome submissions of new solutions, enhancements, and improvements.
Please read through this document to understand how best to contribute.
- Submitting a solution to a case (your implementation, scripts, tooling, documentation, etc.)
- Adding new cases or challenges (with problem statement, constraints, tests or validation)
Contributions that are thoughtful, well-documented, and easy to understand will be much easier to accept.
Each case folder has a solutions subdirectory where you can add your solution and get feedback by creating a pull request.
- Fork the repo to your profile.
- Add your solution inside the
solutionsfolder for the case:- Make sure to include a
README.mdthat explains your solution and how to reproduce it. It doesn’t have to be long — just write something! - It’s best if your
README.mdis in English, but it’s not required. You can also add files in other languages, likeREADME-ru.md. - Feel free to include any other files that will help others understand and test your solution.
- Make sure to include a
- Create a pull request.
That’s all! Your pull request counts as your solution submission. We’ll give you feedback, and if everything looks good, your solution will be merged and shared with the community.
- If you have questions while working on a case, feel free to ask in our Telegram chat
- In your PR, you can also leave a comment or tag maintainers if you need guidance
- You’re welcome to link to your PR in our social / community channel so others can see and comment
Thank you for helping grow this resource and for contributing your knowledge to the community!
We look forward to your solutions, ideas, and feedback.
— The Inview team