-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy the kubeedge api file to the staging directory #5472
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: wbc6080 <wangbincheng4@huawei.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: wbc6080 <wangbincheng4@huawei.com>
Do we need to rename the stage project staging/src/github.com/kubeedge/api, like staging/src/github.com/kubeedge-api? Do we also need to map this folder to a github project? |
Here I refer to the naming method of the api in the staging directory like in kubernetes https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/api, which is directly called the api library. After this PR is merged, an api repo needs to be created, and the code will be synchronized from the staging directory to the api repo. In addition, I have also submitted an application for building the new api repo kubeedge/community#193. @WillardHu |
Ok, I thought this directory |
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Copy the kubeedge api file to the staging directory,and prepare for the subsequent establishment of kubeedge api repo(kubeedge/community#193)
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: