Standardize License Information in mock_engine.go #4121
Conversation
Signed-off-by: lianwg <[email protected]>
|
Hi @lianwg. Thanks for your PR. I'm waiting for a fluid-cloudnative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
|
/lgtm |
|
@LiYuhang9527: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheyang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Ⅰ. Describe what this PR does
The purpose of this pull request is to add or standardize the license information in the header of the mock_engine.go file located at ./pkg/ddc/base/mock/mock_engine.go. I have already made the necessary modifications.
Ⅱ. Does this pull request fix one issue?
NONE
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
NONE
Ⅳ. Describe how to verify it
Clone the repository in your local environment.
Navigate to the ./pkg/ddc/base/mock/ directory.
Open the mock_engine.go file.
Ensure that the license information has been added or standardized in the header of the file.
Ⅴ. Special notes for reviews
Please pay attention to whether the added license information complies with the standard requirements and is correctly placed in the header of the file.
Please modify your pull request description according to the provided template, ensuring that the information accurately and clearly reflects your changes. If you have any further questions, feel free to ask.