add gofmt verify in github ci workflow (#4799)

Signed-off-by: 玖宇 <guotongyu.gty@alibaba-inc.com>
Co-authored-by: 玖宇 <guotongyu.gty@alibaba-inc.com>

Author: Syspretor

.github/workflows/project-check.yml

@@ -62,6 +62,9 @@ jobs:
           echo $(git status --porcelain | grep generated)
           if [ -z "$(git status --porcelain | grep generated)" ]; then echo "openapi validation passed."; else echo "openapi validation failed. Please use 'make gen-openapi' to update openapi"; exit 1; fi
 
+      - name: Code fmt check
+        run: |
+          gofmt -l ./pkg ./cmd ./api | grep . && echo "Please run "make fmt" to verify gofmt" && exit 1 || exit 0
 
       - name: Project lint
         run: |

pkg/ddc/alluxio/master_test.go

@@ -242,10 +242,10 @@ func TestShouldSetupMaster(t *testing.T) {
 // It initializes a fake Kubernetes client with predefined StatefulSet and AlluxioRuntime objects,
 // then verifies whether SetupMaster correctly updates the runtime's status fields.
 // The test ensures that:
-// 1. The SetupMaster function executes without errors.
-// 2. The runtime object is correctly retrieved after execution.
-// 3. The runtime's status is properly updated, including the selector, 
-//    configuration map name, and the presence of conditions.。
+//  1. The SetupMaster function executes without errors.
+//  2. The runtime object is correctly retrieved after execution.
+//  3. The runtime's status is properly updated, including the selector,
+//     configuration map name, and the presence of conditions.。
 func TestSetupMaster(t *testing.T) {
 	statefulSetInputs := []v1.StatefulSet{
 		{

pkg/ddc/alluxio/transform_resources_test.go

@@ -380,23 +380,24 @@ func TestTransformResourcesForWorkerWithValue(t *testing.T) {
 	}
 }
 
-// TestTransformResourcesForWorkerWithOnlyRequest is a unit test function that validates the transformation 
-// of resource requests for Alluxio workers when only resource requests are specified (without limits). 
-// This function ensures that the memory and CPU requests are correctly applied to the worker configuration 
+// TestTransformResourcesForWorkerWithOnlyRequest is a unit test function that validates the transformation
+// of resource requests for Alluxio workers when only resource requests are specified (without limits).
+// This function ensures that the memory and CPU requests are correctly applied to the worker configuration
 // based on the provided resource requests and tiered store settings.
 //
 // Parameters:
 // - t (testing.T): The testing framework used to run the unit test.
 //
 // Returns:
-// - None: The function does not return a value but will report errors if the transformation logic does not
-//   produce the expected results.
+//   - None: The function does not return a value but will report errors if the transformation logic does not
+//     produce the expected results.
 //
 // This test function performs the following steps:
 // 1. Defines resource requests for memory (1Gi) and CPU (500m) with no resource limits.
 // 2. Sets up test cases to validate the transformation logic for two scenarios:
-//      - Scenario 1: A tiered store configuration is provided with a memory quota of 20Gi.
-//      - Scenario 2: No tiered store configuration is provided, and the memory request remains as 1Gi.
+//   - Scenario 1: A tiered store configuration is provided with a memory quota of 20Gi.
+//   - Scenario 2: No tiered store configuration is provided, and the memory request remains as 1Gi.
+//
 // 3. Initializes an AlluxioEngine instance with a fake client and runtime objects for testing.
 // 4. Transforms the resource requirements for the worker using the AlluxioEngine.
 // 5. Validates that the transformed memory requests match the expected values based on the scenarios.

pkg/ddc/alluxio/utils_test.go

@@ -424,7 +424,7 @@ func TestGetRuntime(t *testing.T) {
 }
 
 // TestGetMasterPod verifies the correct retrieval of the master Pod for an Alluxio runtime.
-// This test validates whether the AlluxioEngine's getMasterPod method accurately fetches 
+// This test validates whether the AlluxioEngine's getMasterPod method accurately fetches
 // the expected Pod resource from Kubernetes based on the provided runtime configuration.
 //
 // Test Cases:
@@ -736,14 +736,14 @@ func TestGetWorkerDaemonsetName(t *testing.T) {
 }
 
 // TestGetFuseDaemonsetName is a unit test for the getFuseName method of the AlluxioEngine struct.
-// This test verifies that the method correctly constructs the expected daemonset name 
+// This test verifies that the method correctly constructs the expected daemonset name
 // based on the given engine name.
-// The test defines a struct `fields` containing the engine name and a test case struct 
+// The test defines a struct `fields` containing the engine name and a test case struct
 // that includes the test case name, input fields, and the expected daemonset name.
 // The test case used:
 // - When the engine name is "spark", the expected daemonset name should be "spark-fuse".
-// The test iterates through all defined cases, creates an instance of AlluxioEngine with 
-// the given name, calls the `getFuseName` method, and checks if the returned result matches 
+// The test iterates through all defined cases, creates an instance of AlluxioEngine with
+// the given name, calls the `getFuseName` method, and checks if the returned result matches
 // the expected value. If the result differs, an error message is reported.
 func TestGetFuseDaemonsetName(t *testing.T) {
 	type fields struct {

pkg/ddc/jindo/dataset_test.go

@@ -123,12 +123,12 @@ func TestUpdateCacheOfDataset(t *testing.T) {
 // 3. Proper synchronization of cache states from runtime status
 //
 // Test strategy:
-// - Creates mock Dataset and JindoRuntime objects in a test namespace
-// - Uses a fake Kubernetes client to simulate API server interactions
-// - Verifies three key aspects of DatasetStatus after updates:
-//   a) Phase matches expected state
-//   b) CacheStates are properly propagated from runtime status
-//   c) HCFSStatus fields remain unchanged during phase transitions
+//   - Creates mock Dataset and JindoRuntime objects in a test namespace
+//   - Uses a fake Kubernetes client to simulate API server interactions
+//   - Verifies three key aspects of DatasetStatus after updates:
+//     a) Phase matches expected state
+//     b) CacheStates are properly propagated from runtime status
+//     c) HCFSStatus fields remain unchanged during phase transitions
 //
 // Test cases cover:
 // - Successful bound state update