Skip to content

Commit 543180b

Browse files
committed
DevOps-Interview: docs: Add CONTRIBUTING.md with guidelines for contributions
Signed-off-by: NotHarshhaa <[email protected]>
1 parent 53e9ad3 commit 543180b

File tree

1 file changed

+108
-0
lines changed

1 file changed

+108
-0
lines changed

CONTRIBUTING.md

Lines changed: 108 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,108 @@
1+
# 📜 **CONTRIBUTING** - DevOps Interview Questions Repository
2+
3+
Thank you for considering contributing to **DevOps Interview Questions**! 🎉 This repository is a community-driven effort to provide a **comprehensive collection of 550+ interview questions and answers** covering various **DevOps tools and cloud platforms**. Your contributions help make this resource valuable for DevOps learners and professionals.
4+
5+
---
6+
7+
## 🚀 **How to Contribute**
8+
9+
### 🔹 1. Fork & Clone the Repository
10+
11+
1. Click the **Fork** button (top-right corner) to create a copy of the repository in your GitHub account.
12+
2. Clone the forked repository to your local machine:
13+
14+
```bash
15+
git clone https://github.com/NotHarshhaa/devops-interview-questions.git
16+
cd devops-interview-questions
17+
```
18+
19+
3. Create a new branch for your changes:
20+
21+
```bash
22+
git checkout -b feature/add-new-questions
23+
```
24+
25+
---
26+
27+
### 🔹 2. Types of Contributions
28+
29+
> [!IMPORTANT]
30+
>
31+
> #### **Add New Interview Questions**
32+
>
33+
> - Navigate to the respective category (e.g., AWS, Kubernetes, Docker, etc.).
34+
> - Add your new question in the format:
35+
>
36+
> ```markdown
37+
> ### ❓ Question: How does Kubernetes handle container networking?
38+
> **Answer:** Kubernetes uses CNI (Container Network Interface) plugins to configure networking for pods, allowing communication between containers and external services.
39+
> ```
40+
>
41+
> - Ensure answers are **clear**, **concise**, and **technically correct**.
42+
>
43+
> #### ✅ **Improve Existing Questions & Answers**
44+
>
45+
> - If you find a question that needs better explanation, formatting, or corrections, **edit it**.
46+
> - Add **code snippets** where necessary to improve clarity.
47+
>
48+
> #### ✅ **Fix Typos, Grammar, or Formatting Issues**
49+
>
50+
> - Ensure markdown syntax is correct.
51+
> - Use **proper bullet points, headers, and spacing** for readability.
52+
>
53+
> #### ✅ **Add References & Resources**
54+
>
55+
> - If applicable, add links to **official documentation** or reputable sources for further reading.
56+
57+
---
58+
59+
### 🔹 3. Commit & Push Changes
60+
61+
1. Add your changes:
62+
63+
```bash
64+
git add .
65+
```
66+
67+
2. Commit with a **descriptive message**:
68+
69+
```bash
70+
git commit -m "[DevOps-Interview] feat: Added Kubernetes networking question"
71+
```
72+
73+
3. Push to your forked repository:
74+
75+
```bash
76+
git push origin feature/add-new-questions
77+
```
78+
79+
4. Open a **Pull Request (PR)** on GitHub.
80+
81+
---
82+
83+
## 📌 **Pull Request Guidelines**
84+
85+
> [!TIP]
86+
>
87+
>🔹 **Ensure your PR has a clear title & description**
88+
>🔹 **Follow markdown formatting properly**
89+
>🔹 **Keep PRs focused on a specific topic** (avoid multiple unrelated changes)
90+
>🔹 **Mention any related issues in your PR** (if applicable)
91+
92+
---
93+
94+
## 📢 **Code of Conduct**
95+
96+
> [!NOTE]
97+
>
98+
> By participating in this project, you agree to follow our **[Code of Conduct](CODE_OF_CONDUCT.md)** to maintain a respectful and collaborative environment.
99+
100+
---
101+
102+
## **Support & Acknowledgments**
103+
104+
> [!IMPORTANT]
105+
>
106+
> If you find this repository helpful, please **star** ⭐ it and **spread the word**!
107+
108+
🚀 **Happy Contributing!** 🚀

0 commit comments

Comments
 (0)