You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,13 @@ Please see https://git.k8s.io/community/CLA.md for more info.
24
24
1. Fork the desired repo, develop and test your code changes.
25
25
1. Submit a pull request.
26
26
27
+
In addition to the above steps, we adhere to the following best practices to maintain consistency and efficiency in our project:
28
+
29
+
-**Single Commit per PR:** Each Pull Request (PR) should contain only one commit. This approach simplifies tracking changes and makes the history more readable.
30
+
-**One Issue per PR:** Each PR should address a single specific issue or need. This helps in streamlining our workflow and makes it easier to identify and resolve problems such as revert the changes if required.
31
+
32
+
For more detailed guidelines, refer to the [Kubernetes Contributor Guide][k8s-contrubutiong-guide].
33
+
27
34
## How to build kubebuilder locally
28
35
29
36
Note that, by building the kubebuilder from the source code we are allowed to test the changes made locally.
@@ -198,3 +205,4 @@ Participation in the Kubernetes community is governed by the [Kubernetes Code of
0 commit comments