-
Notifications
You must be signed in to change notification settings - Fork 62
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
Document structs used in API group interfaces #266
Document structs used in API group interfaces #266
Conversation
c5ad275
to
19f67d3
Compare
19f67d3
to
3f6d00f
Compare
/cc @mauriciopoppe Again, sorry about the force pushing. Still learning my way around rebasing and force pushing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexander-ding, mauriciopoppe 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 |
@mauriciopoppe could you close #232. I put the wrong fixes # in the description at first (referenced a closed issue). I edited the description to match the issue we actually are fixing here, but you need to manually close #232. |
0496593 Merge pull request kubernetes-csi#268 from huww98/cloudbuild 119aee1 Merge pull request kubernetes-csi#266 from jsafrane/bump-sanity-5.3.1 0ae5e52 Update cloudbuild image with go 1.21+ 406a79a Merge pull request kubernetes-csi#267 from huww98/gomodcache 9cec273 Set GOMODCACHE to avoid re-download toolchain 43bde06 Bump csi-sanity to 5.3.1 git-subtree-dir: release-tools git-subtree-split: 04965932661b6e62709dcdbb9c25da528bac2605
What type of PR is this?
What this PR does / why we need it:
Documents API structs that are now user facing.
Which issue(s) this PR fixes:
Fixes #232
Special notes for your reviewer:
Does this PR introduce a user-facing change?: